From: Isaac Boukris <iboukris@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: Re: dumpcap: weird failure with six IPv6 hosts in the filter
Date: Mon, 17 Jun 2024 21:32:11 +0300 [thread overview]
Message-ID: <CAC-fF8RCdRtiZiQza5FOZpZBPzTQGyTAJ-6V7tZQCVu5cywUYg@mail.gmail.com> (raw)
In-Reply-To: <CAC-fF8QcWvS-neMUq4HzY1Uh4cPnDFuVVnPLkC8B5ZtcReLTsQ@mail.gmail.com>
On Mon, Jun 17, 2024 at 6:57 PM Isaac Boukris <iboukris@gmail.com> wrote:
>
> On Mon, Jun 17, 2024 at 6:30 PM Stephen Hemminger
> <stephen@networkplumber.org> wrote:
> >
> > On Mon, 17 Jun 2024 10:11:47 +0300
> > Isaac Boukris <iboukris@gmail.com> wrote:
> >
> > > Hi Stephen,
> > >
> > > For instance, the following filter fais as follows (if I omit one host
> > > it works):
> > > -f "host 1::1 or host 1::1 or host 1::1 or host 1::1 or host 1::1 or host 1::1"
> > >
> > > EAL: Error - exiting with code: 1
> > > Cause: Packet dump enable on 0:0000:13:00.0 failed Connection timed out
> > >
> > > On the server side I see:
> > > Jun 16 15:17:08: EAL: failed to send to
> > > (/tmp/dpdk/rte/mp_socket_262131_4a103955de0b7a) due to No such file or
> > > directory
> > > Jun 16 15:17:08: pdump_server(): failed to send to client:No such file
> > > or directory
> > > Jun 16 15:17:08: EAL: Fail to handle message: mp_pdump
> > >
> > > Then subsequent requests fail with (even with no filter):
> > > pdump_register_rx_callbacks(): rx callback for port=0 queue=0, already exists
> > >
> > > I debugged the dpdk-mp-msg thread with gdb, as far as I can tell it
> > > hangs an awful lot of time on rte_bpf_load() (~15 secs in my env), so
> > > the client times out and by the time the server tries to respond the
> > > client socket doesn't exist anymore.
> > >
> > > Thoughts?
> >
> > I tried testing this with current 24.07-rc code base and do not see any problem
> > (don't have real hardware needed to fix vdev to get tap to work).
> >
> > # ./build/app/dpdk-dumpcap -f "host 1::1 or host 1::1 or host 1::1 or host 1::1 or host 1::1 or host 1::1"
> > File: /tmp/dpdk-dumpcap_0_net_tap0_20240617082758.pcapng
> > Capturing on 'net_tap0'
> > Packets captured: 0 ^C
> > Packets received/dropped on interface 'net_tap0': 0/0 (0.0)
>
> Thanks for giving it a try, I had thought it would easily reproduce as
> it does for me (perhaps worth trying adding a host or two).
>
> I'll try a more recent dpdk version (currently running 23.11.0) and
> try to narrow it further otherwise.
Just a quick update that I still see the issue in my env with the
master branch (24.07.0-rc0), I'm now testing by adding the filter to
'sample_filters' in test_bpf.c and running:
time sudo build/app/dpdk-test bpf_convert_autotest
With 5 hosts it takes less than 2 secs, with 6 it takes about 25 secs,
i'll try to strace it maybe.
next prev parent reply other threads:[~2024-06-17 18:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 7:11 Isaac Boukris
2024-06-17 14:44 ` Stephen Hemminger
2024-06-17 15:30 ` Stephen Hemminger
2024-06-17 15:57 ` Isaac Boukris
2024-06-17 18:32 ` Isaac Boukris [this message]
2024-06-17 19:37 ` Isaac Boukris
2024-06-17 20:43 ` Isaac Boukris
2024-06-17 21:40 ` Stephen Hemminger
2024-06-18 23:06 ` Konstantin Ananyev
2024-06-19 8:45 ` Isaac Boukris
2024-06-28 16:42 ` Konstantin Ananyev
2024-06-28 16:52 ` Isaac Boukris
2024-06-28 17:05 ` Konstantin Ananyev
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=CAC-fF8RCdRtiZiQza5FOZpZBPzTQGyTAJ-6V7tZQCVu5cywUYg@mail.gmail.com \
--to=iboukris@gmail.com \
--cc=stephen@networkplumber.org \
--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).