From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Sai Aung Hlyan Htet <saiaunghlyanhtet2003@gmail.com>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
netdev@vger.kernel.org, Jesper Dangaard Brouer <hawk@kernel.org>,
Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Subject: Re: [bpf-next,v3] bpf: cpumap: report queue_index to xdp_rxq_info
Date: Wed, 14 Jan 2026 13:33:56 +0100 [thread overview]
Message-ID: <87zf6gz83v.fsf@toke.dk> (raw)
In-Reply-To: <CAGF5Uf7FiD_RQoFx9qLeOaCMH8QC0-n=ozg631g_5QVRHLZ27Q@mail.gmail.com>
Sai Aung Hlyan Htet <saiaunghlyanhtet2003@gmail.com> writes:
> On Wed, Jan 14, 2026 at 8:39 PM Toke Høiland-Jørgensen <toke@redhat.com> wrote:
>
>> Yeah, this has been discussed as well :)
>>
>> See:
>> https://netdevconf.info/0x19/sessions/talk/traits-rich-packet-metadata.html
>>
>> Which has since evolved a bit to these series:
>>
>> https://lore.kernel.org/r/20260105-skb-meta-safeproof-netdevs-rx-only-v2-0-a21e679b5afa@cloudflare.com
>>
>> https://lore.kernel.org/r/20260110-skb-meta-fixup-skb_metadata_set-calls-v1-0-1047878ed1b0@cloudflare.com
>>
>> (Also, please don't top-post on the mailing lists)
>>
>> -Toke
>>
>
> Thanks for the pointers. It is really great to see this series. One
> question: Would adding queue_index to the packet traits KV store be
> a useful follow-up once the core infrastructure lands?
Possibly? Depends on where things land, I suppose. I'd advise following
the discussion on the list until it does :)
-Toke
next prev parent reply other threads:[~2026-01-14 12:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 6:04 [bpf-next,v3] bpf: cpumap: report queue_index to xdp_rxq_info saiaunghlyanhtet
2026-01-14 10:53 ` Toke Høiland-Jørgensen
2026-01-14 11:27 ` Sai Aung Hlyan Htet
2026-01-14 11:38 ` Toke Høiland-Jørgensen
2026-01-14 12:01 ` Sai Aung Hlyan Htet
2026-01-14 12:33 ` Toke Høiland-Jørgensen [this message]
2026-01-14 13:11 ` Sai Aung Hlyan Htet
2026-01-14 13:30 ` Jesper Dangaard Brouer
2026-01-14 14:18 ` Sai Aung Hlyan Htet
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=87zf6gz83v.fsf@toke.dk \
--to=toke@redhat.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=lorenzo.bianconi@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=saiaunghlyanhtet2003@gmail.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