[dpdk-dev] [PATCH] fbarray: add internal tailq for mapped areas

[Stojaczyk, Dariusz]

This patch caused a regression. Any secondary process fails to initialize.
Please see the quick fix here: http://patchwork.dpdk.org/patch/51882/

D.

> -----Original Message-----
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Thursday, March 28, 2019 9:45 PM
> To: Burakov, Anatoly <anatoly.burakov at intel.com>
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] fbarray: add internal tailq for mapped areas
> 
> 26/02/2019 18:13, Anatoly Burakov:
> > Currently, there are numerous reliability issues with fbarray,
> > such as:
> > - There is no way to prevent attaching to overlapping memory
> >   areas
> > - There is no way to prevent double-detach
> > - Failed destroy leaves fbarray in an invalid state (fbarray
> >   itself is valid, but its backing memory area is already
> >   detached)
> >
> > In addition, on FreeBSD, doing mmap() on a file descriptor
> > does not keep the lock, so we also need to store the fd
> > in order to keep the lock.
> >
> > This patch improves upon fbarray to address both of these
> > issues by adding an internal tailq to track allocated areas
> > and their respective file descriptors.
> >
> > Signed-off-by: Anatoly Burakov <anatoly.burakov at intel.com>
> 
> Applied, thanks
> 
>