Re: [dpdk-dev] [PATCH 0/5] lib/ring: templates to support custom element size

2019-08-28 Thread Honnappa Nagarahalli
> Subject: RE: [dpdk-dev] [PATCH 0/5] lib/ring: templates to support custom > element size > > Hi Honnappa, > > Great idea I think we can replace duplicated implementation > lib/librte_eventdev/rte_event_ring.h which uses element sizeof 16B. > There are already a

Re: [dpdk-dev] [PATCH 0/5] lib/ring: templates to support custom element size

2019-08-28 Thread Pavan Nikhilesh Bhagavatula
>ruifeng.w...@arm.com; n...@arm.com >Subject: [dpdk-dev] [PATCH 0/5] lib/ring: templates to support custom >element size >

Re: [dpdk-dev] [PATCH 0/5] lib/ring: templates to support custom element size

2019-08-28 Thread Jerin Jacob Kollanukkaran
ha...@arm.com > Cc: dev@dpdk.org; dharmik.thak...@arm.com; gavin...@arm.com; > ruifeng.w...@arm.com; n...@arm.com > Subject: [dpdk-dev] [PATCH 0/5] lib/ring: templates to support custom element > size > > The current rte_ring hard-codes the type of the ring element to 'void

[dpdk-dev] [PATCH 0/5] lib/ring: templates to support custom element size

2019-08-28 Thread Honnappa Nagarahalli
The current rte_ring hard-codes the type of the ring element to 'void *', hence the size of the element is hard-coded to 32b/64b. Since the ring element type is not an input to rte_ring APIs, it results in couple of issues: 1) If an application requires to store an element which is not 64b, it