From: Martin KaFai Lau <martin.lau@linux.dev>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, netdev@vger.kernel.org,
magnus.karlsson@intel.com, stfomichev@gmail.com,
kerneljasonxing@gmail.com
Subject: Re: [PATCH v2 bpf-next 0/3] xsk: refactors around generic xmit side
Date: Fri, 26 Sep 2025 12:48:34 -0700 [thread overview]
Message-ID: <13ddb0d3-7441-43d9-b8e4-2c8f4acf99bf@linux.dev> (raw)
In-Reply-To: <20250925160009.2474816-1-maciej.fijalkowski@intel.com>
On 9/25/25 9:00 AM, Maciej Fijalkowski wrote:
> this small patchset is about refactoring code around xsk_build_skb() as
> it became pretty heavy. Generic xmit is a bit hard to follow so here are
> three clean ups to start with making this code more friendly.
Acked-by: Martin KaFai Lau <martin.lau@kernel.org>
Hi Jakub, the bpf-next/net tree is currently empty for the upcoming merge
window. Could you help by taking it directly to the net-next tree?
or I can also take it to bpf-next/master.
Thanks,
Martin
next prev parent reply other threads:[~2025-09-26 19:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 16:00 [PATCH v2 bpf-next 0/3] xsk: refactors around generic xmit side Maciej Fijalkowski
2025-09-25 16:00 ` [PATCH v2 bpf-next 1/3] xsk: avoid overwriting skb fields for multi-buffer traffic Maciej Fijalkowski
2025-09-25 18:28 ` Stanislav Fomichev
2025-09-25 23:45 ` Jason Xing
2025-09-25 16:00 ` [PATCH v2 bpf-next 2/3] xsk: remove @first_frag from xsk_build_skb() Maciej Fijalkowski
2025-09-25 18:28 ` Stanislav Fomichev
2025-09-26 0:09 ` Jason Xing
2025-09-25 16:00 ` [PATCH v2 bpf-next 3/3] xsk: wrap generic metadata handling onto separate function Maciej Fijalkowski
2025-09-26 19:48 ` Martin KaFai Lau [this message]
2025-09-26 20:54 ` [PATCH v2 bpf-next 0/3] xsk: refactors around generic xmit side Jakub Kicinski
2025-09-26 21:00 ` patchwork-bot+netdevbpf
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=13ddb0d3-7441-43d9-b8e4-2c8f4acf99bf@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=stfomichev@gmail.com \
/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).