Adding new fields to xsk_tx_metadata

Adding new fields to xsk_tx_metadata

[tianmuyang]

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？
2. Is it appropriate to add such fields(like gso_type) to xsk_tx_metadata？Since current fields seem to be generally hardware-related.

Thanks！

Re: Adding new fields to xsk_tx_metadata

[Stanislav Fomichev]

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.