From: Muyang Tian <tianmuyang@huawei.com>
To: <bpf@vger.kernel.org>
Cc: "David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Donald Hunter" <donald.hunter@gmail.com>,
"Björn Töpel" <bjorn@kernel.org>,
"Magnus Karlsson" <magnus.karlsson@intel.com>,
"Maciej Fijalkowski" <maciej.fijalkowski@intel.com>,
"Jonathan Lemon" <jonathan.lemon@gmail.com>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Jesper Dangaard Brouer" <hawk@kernel.org>,
"John Fastabend" <john.fastabend@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, yanan@huawei.com,
xiesongyang@huawei.com, wuchangye@huawei.com,
liuxin350@huawei.com, zhangmingyi5@huawei.com,
liwei883@huawei.com, tianmuyang@huawei.com
Subject: [PATCH bpf-next v2 0/3] XDP metadata: Rx checksum/GSO hint; Tx GSO offload
Date: Fri, 18 Oct 2024 17:14:59 +0800 [thread overview]
Message-ID: <20241018091502.411513-1-tianmuyang@huawei.com> (raw)
This series introduce XDP metadata functionality, including Rx checksum/GSO hint
and Tx GSO offload. This is aimed to transfer control fields when processing jumbo
frames between VMs.
v1:
https://lore.kernel.org/all/20241017135430.51655-1-tianmuyang@huawei.com/
Changes since v1:
- add reference to previous work[1] in patch 1/3
[1] https://lore.kernel.org/bpf/20230811161509.19722-13-larysa.zaremba@intel.com/
Muyang Tian (3):
xdp: Add Rx checksum hint
xdp: Add Rx GSO hint
xsk: Add Tx GSO type and size offload support
Documentation/netlink/specs/netdev.yaml | 12 +++++
Documentation/networking/xdp-rx-metadata.rst | 6 +++
include/net/xdp.h | 50 ++++++++++++++++++++
include/net/xdp_sock.h | 8 ++++
include/net/xdp_sock_drv.h | 1 +
include/uapi/linux/if_xdp.h | 11 +++++
include/uapi/linux/netdev.h | 8 ++++
net/core/xdp.c | 41 ++++++++++++++++
net/xdp/xsk.c | 5 ++
tools/include/uapi/linux/if_xdp.h | 11 +++++
tools/include/uapi/linux/netdev.h | 8 ++++
11 files changed, 161 insertions(+)
--
2.41.0
next reply other threads:[~2024-10-18 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 9:14 Muyang Tian [this message]
2024-10-18 9:15 ` [PATCH bpf-next v2 1/3] xdp: Add Rx checksum hint Muyang Tian
2024-10-18 9:15 ` [PATCH bpf-next v2 2/3] xdp: Add Rx GSO hint Muyang Tian
2024-10-18 9:15 ` [PATCH bpf-next v2 3/3] xsk: Add Tx GSO type and size offload support Muyang Tian
2024-10-18 16:39 ` [PATCH bpf-next v2 0/3] XDP metadata: Rx checksum/GSO hint; Tx GSO offload Stanislav Fomichev
2024-10-20 20:51 ` Willem de Bruijn
2024-10-21 12:04 ` Magnus Karlsson
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=20241018091502.411513-1-tianmuyang@huawei.com \
--to=tianmuyang@huawei.com \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuxin350@huawei.com \
--cc=liwei883@huawei.com \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wuchangye@huawei.com \
--cc=xiesongyang@huawei.com \
--cc=yanan@huawei.com \
--cc=zhangmingyi5@huawei.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