On 2023-04-19 13:06, Jerin Jacob wrote:
> On Mon, Apr 17, 2023 at 9:06 PM Mattias Rönnblom
> wrote:
>>
>> On 2023-04-17 14:52, Jerin Jacob wrote:
>>> On Thu, Apr 13, 2023 at 12:24 PM Mattias Rönnblom
>>> wrote:
void
rte_event_return_new_credits(...);
Thoughts?
>>>
>>
On Mon, Apr 17, 2023 at 9:06 PM Mattias Rönnblom
wrote:
>
> On 2023-04-17 14:52, Jerin Jacob wrote:
> > On Thu, Apr 13, 2023 at 12:24 PM Mattias Rönnblom
> > wrote:
> >>
> >>
> >> void
> >> rte_event_return_new_credits(...);
> >>
> >> Thoughts?
> >
> > I see the following cons on this approach.
>
On 2023-04-17 14:52, Jerin Jacob wrote:
> On Thu, Apr 13, 2023 at 12:24 PM Mattias Rönnblom
> wrote:
>>
>>
>> void
>> rte_event_return_new_credits(...);
>>
>> Thoughts?
>
> I see the following cons on this approach.
>
Does the use case in my original e-mail seem like a reasonable one to
you? I
On Thu, Apr 13, 2023 at 12:24 PM Mattias Rönnblom
wrote:
>
>
> void
> rte_event_return_new_credits(...);
>
> Thoughts?
I see the following cons on this approach.
# Adding multiple APIs in fast path to driver layer may not
performance effective solution.
# At least for cnxk HW, credits are for de
Hi,
This interaction with eventdev introduces some overhead. Isn't it easier to
just create an API to query the available credit for a certain event port?
Regards,
Heng
-Original Message-
From: Mattias Rönnblom
Sent: Thursday, April 13, 2023 8:54 AM
To: Jerin Jacob Kollanukkaran
Cc:
5 matches
Mail list logo