Re: [dpdk-dev] [PATCH v5 0/8] Introduce event vectorization

2021-03-24 Thread Jayatheerthan, Jay
p.com; Van Haaren, Harry > ; mattias.ronnblom > ; Ma, Liang J > Cc: dev@dpdk.org > Subject: RE: [dpdk-dev] [PATCH v5 0/8] Introduce event vectorization > > >> From: pbhagavat...@marvell.com > >> Sent: Wednesday, March 24, 2021 10:35 AM > >> To: jer...@marvell.com; Jayat

Re: [dpdk-dev] [PATCH v5 0/8] Introduce event vectorization

2021-03-23 Thread Pavan Nikhilesh Bhagavatula
nblom >; Ma, Liang J > >> Cc: dev@dpdk.org; Pavan Nikhilesh >> Subject: [dpdk-dev] [PATCH v5 0/8] Introduce event vectorization >> >> From: Pavan Nikhilesh >> >> In traditional event programming model, events are identified by a >> flow-id and

Re: [dpdk-dev] [PATCH v5 0/8] Introduce event vectorization

2021-03-23 Thread Jayatheerthan, Jay
mattias.ronnblom > ; Ma, Liang J > Cc: dev@dpdk.org; Pavan Nikhilesh > Subject: [dpdk-dev] [PATCH v5 0/8] Introduce event vectorization > > From: Pavan Nikhilesh > > In traditional event programming model, events are identified by a > flow-id and a uintptr_t. The flow-id un

[dpdk-dev] [PATCH v5 0/8] Introduce event vectorization

2021-03-23 Thread pbhagavatula
From: Pavan Nikhilesh In traditional event programming model, events are identified by a flow-id and a uintptr_t. The flow-id uniquely identifies a given event and determines the order of scheduling based on schedule type, the uintptr_t holds a single object. Event devices also support burst mod