From: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
To: Isaac Boukris <iboukris@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>, users@dpdk.org
Subject: Re: dumpcap: weird failure with six IPv6 hosts in the filter
Date: Fri, 28 Jun 2024 17:42:06 +0100 [thread overview]
Message-ID: <a7fd30b4-1686-4a53-8c19-b0fc03ba87f5@yandex.ru> (raw)
In-Reply-To: <CAC-fF8Q-skxidzWZMz6V6rMyhfZKERdpHZdNb2E7tPGGe9obag@mail.gmail.com>
Hi Isaac,
>
> On Wed, Jun 19, 2024 at 2:06 AM Konstantin Ananyev
> <konstantin.v.ananyev@yandex.ru> wrote:
>>
>> 17.06.2024 22:40, Stephen Hemminger пишет:
>>> On Mon, 17 Jun 2024 23:43:19 +0300
>>> Isaac Boukris <iboukris@gmail.com> wrote:
>>>
>>>> On Mon, Jun 17, 2024 at 10:37 PM Isaac Boukris <iboukris@gmail.com> wrote:
>>>>>
>>>>>> 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.
>>>>>
>>>>> strace was useless, no syscalls for ~18 secs, not sure how to debug it
>>>>> further, valgrind / callgrind don't work on dpdk..
>>>>>
>>>>> It doesn't seem to be about the size though, I was able to produce
>>>>> larger bpf code with ipv4 addresses and it worked fine too.
>>>>
>>>> Debugged a bit further with gdb, it looks like it is stuck in a while
>>>> loop in lib/bpf/bpf_validate.c:evaluate(), there is a comment saying
>>>> "make sure we evaluate each node only once" but it seem to go back and
>>>> forth on the same idx's afaict.
>>>
>>> No idea, only original author understands the verifier.
>>> Having our own unique verifier may not be a good idea.
>>> There some other userspace BPF projects, seems like a good place for
>>> convergence.
>>>
>>>
>>> https://lpc.events/event/17/contributions/1639/attachments/1280/2585/userspace-ebpf-bpftime-lpc.pdf
>>
>> hi Isaac,
>> please create a bug report in DPDK bugzilla.
>> Ideally with a clear and simple way to reproduce
>> the bug you are facing in the description.
>> I'll try to have a look when I'll have some free time.
>> Thanks
>> Konstantin
>
> Done:
>
> https://bugs.dpdk.org/show_bug.cgi?id=1465
In case you didn't get update from the bugzilla,
here is a patch to try, when you'll get a chance:
http://patchwork.dpdk.org/project/dpdk/list/?series=32321
Thanks
Konstantin
>
> Thanks a lot!
next prev parent reply other threads:[~2024-06-28 16:42 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
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 [this message]
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=a7fd30b4-1686-4a53-8c19-b0fc03ba87f5@yandex.ru \
--to=konstantin.v.ananyev@yandex.ru \
--cc=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).