From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: Re: [PATCH] net/tap: do not force inline or unroll
Date: Wed, 4 Jun 2025 15:05:00 -0700 [thread overview]
Message-ID: <20250604150500.5f8c799a@hermes.local> (raw)
In-Reply-To: <5348112.44csPzL39Z@thomas>
On Wed, 04 Jun 2025 11:27:18 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:
> 24/04/2025 18:07, Stephen Hemminger:
> > The BPF code in TAP device was using outdated advice on how
> > to write BPF programs. Modern BPF verifier has to do less work
> > if force inlining and unrolling is not done.
>
> Why do you keep unroll in IPv6 parsing?
>
>
Good catch.
prev parent reply other threads:[~2025-06-04 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 16:07 Stephen Hemminger
2025-06-04 9:27 ` Thomas Monjalon
2025-06-04 22:05 ` Stephen Hemminger [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:
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=20250604150500.5f8c799a@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).