On 2019-12-06 23:22, Venky Venkatesh wrote:
To my understanding, per eventdev API, events are considered in flight
between NEW to RELEASE (implicit/explicit).
DSW considers events to be in flight between time of enqueue (on the
source port), to the time of release (on the destination port). Th
To my understanding, per eventdev API, events are considered in flight
between NEW to RELEASE (implicit/explicit). Now consider an event (event-1)
going thru the following stages:
1. NEW from core-3
2. dequeued by core-1
3. FORWARD
4. core-1 does a next dequeue
5. dequeued by core-2
On 2019-12-06 17:32, Venky Venkatesh wrote:
Thanks Mattias for the clarifications.
1 more question: This time it is about the inflight accounting for DSW.
Here is my understanding: it seems to consider only the events which
are *inside
the scheduler* as in flight.
Yes, like all event devices,
Thanks Mattias for the clarifications.
1 more question: This time it is about the inflight accounting for DSW.
Here is my understanding: it seems to consider only the events which
are *inside
the scheduler* as in flight. I am trying to distinguish it from those which
have been currently given to c
On 2019-12-06 01:26, Venky Venkatesh wrote:
I see that the provision in 18.11 eventdev DSW for maximum number of queues
is
#define DSW_MAX_QUEUES (16)
1. If the number of queues needed is to be increased to 7 bits (i.e.
128) is there any issue (correctness, scale, performance) other t
+ DSW maintainer
On Fri, Dec 6, 2019 at 5:57 AM Venky Venkatesh
wrote:
>
> I see that the provision in 18.11 eventdev DSW for maximum number of queues
> is
>
> #define DSW_MAX_QUEUES (16)
>
>
>
>1. If the number of queues needed is to be increased to 7 bits (i.e.
>128) is there any issue
6 matches
Mail list logo
