From: Stephen Hemminger <stephen@networkplumber.org>
To: Isaac Boukris <iboukris@gmail.com>
Cc: users@dpdk.org
Subject: Re: dumpcap: weird failure with six IPv6 hosts in the filter
Date: Mon, 17 Jun 2024 07:44:13 -0700 [thread overview]
Message-ID: <20240617074413.46af9fca@hermes.local> (raw)
In-Reply-To: <CAC-fF8S8KL_d4QPWuQL+vAsQAfjnPA1m7hNP830qobHJ-4J3eA@mail.gmail.com>
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?
>
> Thanks!
What is the resulting bpf code? Looks like a BPF bug with larger programs.
next prev parent reply other threads:[~2024-06-17 14:44 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 [this message]
2024-06-17 15:30 ` Stephen Hemminger
2024-06-17 15:57 ` Isaac Boukris
2024-06-17 18:32 ` Isaac Boukris
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=20240617074413.46af9fca@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).