From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [PATCH] net/tap: do not force inline or unroll
Date: Wed, 04 Jun 2025 11:27:18 +0200 [thread overview]
Message-ID: <5348112.44csPzL39Z@thomas> (raw)
In-Reply-To: <20250424160705.19655-1-stephen@networkplumber.org>
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?
next prev parent reply other threads:[~2025-06-04 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 16:07 [PATCH] net/tap: do not force inline or unroll Stephen Hemminger
2025-06-04 9:27 ` Thomas Monjalon [this message]
2025-06-04 22:05 ` Stephen Hemminger
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=5348112.44csPzL39Z@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.