[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <IA3PR11MB9254FD76B5402AE44F2CAC13D856A@IA3PR11MB9254.namprd11.prod.outlook.com>
Date: Wed, 16 Jul 2025 02:05:04 +0000
From: "Song, Yoong Siang" <yoong.siang.song@...el.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: "David S . Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Simon Horman
<horms@...nel.org>, Jonathan Corbet <corbet@....net>, Alexei Starovoitov
<ast@...nel.org>, Daniel Borkmann <daniel@...earbox.net>, "Jesper Dangaard
Brouer" <hawk@...nel.org>, John Fastabend <john.fastabend@...il.com>,
Stanislav Fomichev <sdf@...ichev.me>, "netdev@...r.kernel.org"
<netdev@...r.kernel.org>, "linux-doc@...r.kernel.org"
<linux-doc@...r.kernel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "bpf@...r.kernel.org" <bpf@...r.kernel.org>
Subject: RE: [PATCH bpf-next,v4 1/1] doc: clarify XDP Rx metadata handling and
driver requirements
On Wednesday, July 16, 2025 7:49 AM, Jakub Kicinski <kuba@...nel.org> wrote:
>On Tue, 15 Jul 2025 15:15:02 +0800 Song Yoong Siang wrote:
>> -An XDP program can store individual metadata items into this ``data_meta``
>> +Certain devices may utilize the ``data_meta`` area for specific purposes.
>
>Calling headroom "``data_meta`` area" is confusing, IMO. I'd say:
>
> Certain devices may prepend metadata to received packets.
>
>And the rest of this paragraph can stay as is.
>
Noted. Will rework accordingly.
>> +Drivers for these devices must move any hardware-related metadata out from
>the
>> +``data_meta`` area before presenting the frame to the XDP program. This ensures
>> +that the XDP program can store individual metadata items into this ``data_meta``
Powered by blists - more mailing lists