DPDK usage discussions
 help / color / mirror / Atom feed
From: Isaac Boukris <iboukris@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: Re: Concurrent invocations of the dpdk-dumpcap tool
Date: Sun, 17 Sep 2023 09:37:06 +0300	[thread overview]
Message-ID: <CAC-fF8RZfuc15YP-9e6gkLxdAaEFyzASNgO2pn9XMDO6BDa5qw@mail.gmail.com> (raw)
In-Reply-To: <20230916190119.100e3ac9@hermes.local>

On Sun, Sep 17, 2023 at 5:01 AM Stephen Hemminger
<stephen@networkplumber.org> wrote:
> On Sun, 17 Sep 2023 00:11:31 +0300
> Isaac Boukris <iboukris@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?

      reply	other threads:[~2023-09-17  6:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-16 21:11 Isaac Boukris
2023-09-17  2:01 ` Stephen Hemminger
2023-09-17  6:37   ` Isaac Boukris [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAC-fF8RZfuc15YP-9e6gkLxdAaEFyzASNgO2pn9XMDO6BDa5qw@mail.gmail.com \
    --to=iboukris@gmail.com \
    --cc=stephen@networkplumber.org \
    --cc=users@dpdk.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).