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

2019-03-28 Thread Stojaczyk, Dariusz
5 PM > To: Burakov, Anatoly > Cc: dev@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

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

2019-03-28 Thread Thomas Monjalon
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 > its

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

2019-02-26 Thread 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 alre