nstantin
> ; Gavin Hu (Arm Technology China)
> ; nd
> Subject: Re: [dpdk-dev] [PATCH v4 2/2] mempool/nb_stack: add non-blocking
> stack mempool
>
> 19/01/2019 01:00, Eads, Gage:
> > > > I am wondering if it makes sense to decouple the NB stack data
> > > >
19/01/2019 01:00, Eads, Gage:
> > > I am wondering if it makes sense to decouple the NB stack data
> > > structure from mempool driver (similar to rte_ring)? I see that stack
> > > based mempool implements the stack data structure in the driver. But,
> > > NB stack might not be such a trivial data
ina)
> ; nd ; nd
> Subject: RE: [dpdk-dev] [PATCH v4 2/2] mempool/nb_stack: add non-blocking
> stack mempool
>
>
>
> > -Original Message-
> > From: Honnappa Nagarahalli [mailto:honnappa.nagaraha...@arm.com]
> > Sent: Thursday, January 17, 2019 11:05
> ; Gavin Hu (Arm Technology China)
> ; nd ; Honnappa Nagarahalli
> ; nd
> Subject: RE: [dpdk-dev] [PATCH v4 2/2] mempool/nb_stack: add non-blocking
> stack mempool
>
> Hi Gage,
> Thank you for your contribution on non-blocking data structures. I think
> they
> are im
Hi Gage,
Thank you for your contribution on non-blocking data structures. I think
they are important to extend DPDK into additional use cases.
I am wondering if it makes sense to decouple the NB stack data structure from
mempool driver (similar to rte_ring)? I see that stack based mempool i
This commit adds support for non-blocking (linked list based) stack mempool
handler. The stack uses a 128-bit compare-and-swap instruction, and thus is
limited to x86_64. The 128-bit CAS atomically updates the stack top pointer
and a modification counter, which protects against the ABA problem.
In
6 matches
Mail list logo
