From: Stephen Hemminger <stephen@networkplumber.org>
To: Isaac Boukris <iboukris@gmail.com>
Cc: users@dpdk.org
Subject: Re: Concurrent invocations of the dpdk-dumpcap tool
Date: Sat, 16 Sep 2023 19:01:19 -0700 [thread overview]
Message-ID: <20230916190119.100e3ac9@hermes.local> (raw)
In-Reply-To: <CAC-fF8QQD5LSZ-c=4Egs2qjobd=4CLWHu+9BrqQiS==_R558iA@mail.gmail.com>
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.
next prev parent reply other threads:[~2023-09-17 2:01 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 [this message]
2023-09-17 6:37 ` Isaac Boukris
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230916190119.100e3ac9@hermes.local \
--to=stephen@networkplumber.org \
--cc=iboukris@gmail.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).