From: Stanislav Fomichev <stfomichev@gmail.com>
To: tianmuyang <tianmuyang@huawei.com>
Cc: "alan.maguire@oracle.com" <alan.maguire@oracle.com>,
"andrii@kernel.org" <andrii@kernel.org>,
"arnaldo.melo@gmail.com" <arnaldo.melo@gmail.com>,
"ast@kernel.org" <ast@kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
"dwarves@vger.kernel.org" <dwarves@vger.kernel.org>,
"kernel-team@fb.com" <kernel-team@fb.com>,
"ndesaulniers@google.com" <ndesaulniers@google.com>,
"yonghong.song@linux.dev" <yonghong.song@linux.dev>,
"Yanan (Euler)" <yanan@huawei.com>,
"Wuchangye (EulerOS)" <wuchangye@huawei.com>,
Xiesongyang <xiesongyang@huawei.com>,
"kongweibin (A)" <kongweibin2@huawei.com>,
"zhangmingyi (C)" <zhangmingyi5@huawei.com>,
"liwei (H)" <liwei883@huawei.com>
Subject: Re: Adding new fields to xsk_tx_metadata
Date: Wed, 11 Sep 2024 07:39:32 -0700 [thread overview]
Message-ID: <ZuGrpG6N_OINizBm@mini-arch> (raw)
In-Reply-To: <7835e88690ad424cbf644bf3cb0610b5@huawei.com>
On 09/11, tianmuyang wrote:
> Hi all:
> We want to add some fields to xsk_tx_metadata such as gso_type & gso_size, in order to transfer control fields when handling jumbo frames passing between VMs. My questions are:
> 1. Has the community discussed about adding new fields to xsk_tx_metadata？
There has been some discussion of exploring AF_XDP segmentation offloads in
https://lore.kernel.org/bpf/3190e03c-ea5d-69fb-48e5-6cc45b1ed521@redhat.com/
> 2. Is it appropriate to add such fields(like gso_type) to xsk_tx_metadata？Since current fields seem to be generally hardware-related.
GSO is also HW-related. GSO does all the plumbing to allow the stack use
HW segmentation. So, in the end, if we end up exposing it to AF_XDP,
there has to be some HW (or driver) that implements the support.
prev parent reply other threads:[~2024-09-11 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 3:43 Adding new fields to xsk_tx_metadata tianmuyang
2024-09-11 14:39 ` Stanislav Fomichev [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=ZuGrpG6N_OINizBm@mini-arch \
--to=stfomichev@gmail.com \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dwarves@vger.kernel.org \
--cc=kernel-team@fb.com \
--cc=kongweibin2@huawei.com \
--cc=liwei883@huawei.com \
--cc=ndesaulniers@google.com \
--cc=tianmuyang@huawei.com \
--cc=wuchangye@huawei.com \
--cc=xiesongyang@huawei.com \
--cc=yanan@huawei.com \
--cc=yonghong.song@linux.dev \
--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 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.