Concurrent invocations of the dpdk-dumpcap tool

[Isaac Boukris]

On Sun, Sep 17, 2023 at 5:01 AM Stephen Hemminger
<stephen at networkplumber.org> wrote:
>
> On Sun, 17 Sep 2023 00:11:31 +0300
> Isaac Boukris <iboukris at gmail.com> wrote:
>
> > I'm testing with the 22.11.3 version code (latest LTS) but there don't
> > seem to be significant changes in master.
> >
> > Given the above I had the hunch the ring names collide in shared
> > memory, so I changed both the ring and the pool names in the dumpcap
> > tool to include the pid, and with that the above scenario works fine
> > as expected, is that a proper fix?
>
> If you have two processes trying to capture on same interface it
> isn't going to work because both will be fighting over the same
> ring of packets. To make it work would require more extensive changes
> where multiple copies of packet are made.

Specifically, the scenario of the crash is when trying to capture on
different interfaces. By running more tests it seems that what fixes
the crash is actually adding the pid to the name of the mem-pool (not
the ring). Should I submit a patch with that?