From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Muyang Tian <tianmuyang@huawei.com>
Cc: "Larysa Zaremba" <larysa.zaremba@intel.com>,
bpf@vger.kernel.org, "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
Subject: Re: [PATCH 1/3] xdp: Add Rx checksum hint
Date: Thu, 17 Oct 2024 16:27:50 +0200 [thread overview]
Message-ID: <ff067123-f516-4e86-bdeb-c7fcb5cef796@intel.com> (raw)
In-Reply-To: <20241017135430.51655-2-tianmuyang@huawei.com>
From: Muyang Tian <tianmuyang@huawei.com>
Date: Thu, 17 Oct 2024 21:54:28 +0800
> This is an implementation of functionality that allows drivers
> to expose checksum information to XDP.
> This information includes:
> - Checksum info, a union of
> - complete checksum, if checksum is complete
> - skb-style checksum start and offset, if checksum is partial
> - Checksum status, an enum which is the same as skb checksums in
> skbuff.h, identical to sk_buff.ip_summed
>
> Signed-off-by: Muyang Tian <tianmuyang@huawei.com>
Is it just me or this is clearly based on [0] sent a year ago?
Credits then?
> ---
> Documentation/netlink/specs/netdev.yaml | 4 +++
> Documentation/networking/xdp-rx-metadata.rst | 3 ++
> include/net/xdp.h | 38 ++++++++++++++++++++
> include/uapi/linux/netdev.h | 3 ++
> net/core/xdp.c | 23 ++++++++++++
> tools/include/uapi/linux/netdev.h | 3 ++
> 6 files changed, 74 insertions(+)
[0]
https://lore.kernel.org/bpf/20230927075124.23941-13-larysa.zaremba@intel.com
Thanks,
Olek
next prev parent reply other threads:[~2024-10-17 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 13:54 [PATCH 0/3] XDP metadata: Rx checksum/GSO hint; Tx GSO offload Muyang Tian
2024-10-17 13:54 ` [PATCH 1/3] xdp: Add Rx checksum hint Muyang Tian
2024-10-17 14:27 ` Alexander Lobakin [this message]
2024-10-18 9:07 ` Muyang Tian
2024-10-17 13:54 ` [PATCH 2/3] xdp: Add Rx GSO hint Muyang Tian
2024-10-17 13:54 ` [PATCH 3/3] xsk: Add Tx GSO type and size offload support Muyang Tian
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=ff067123-f516-4e86-bdeb-c7fcb5cef796@intel.com \
--to=aleksander.lobakin@intel.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=larysa.zaremba@intel.com \
--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=tianmuyang@huawei.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