From: "Toke Høiland-Jørgensen" <toke@kernel.org>
To: saiaunghlyanhtet <saiaunghlyanhtet2003@gmail.com>, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
netdev@vger.kernel.org,
saiaunghlyanhtet <saiaunghlyanhtet2003@gmail.com>,
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 11:53:42 +0100 [thread overview]
Message-ID: <87h5so1n49.fsf@toke.dk> (raw)
In-Reply-To: <20260114060430.1287640-1-saiaunghlyanhtet2003@gmail.com>
saiaunghlyanhtet <saiaunghlyanhtet2003@gmail.com> writes:
> When packets are redirected via cpumap, the original queue_index
> information from xdp_rxq_info was lost. This is because the
> xdp_frame structure did not include a queue_index field.
>
> This patch adds a queue_index field to struct xdp_frame and ensures
> it is properly preserved during the xdp_buff to xdp_frame conversion.
> Now the queue_index is reported to the xdp_rxq_info.
>
> Resolves the TODO comment in cpu_map_bpf_prog_run_xdp().
>
> Signed-off-by: saiaunghlyanhtet <saiaunghlyanhtet2003@gmail.com>
This exact patch was submitted before by Lorenzo[0] and was rejected
with the argument that we shouldn't be adding more fields to xdp_frame
in an ad-hoc manner, but rather wait until we have a more general
solution.
-Toke
[0] https://lore.kernel.org/r/1a22e7e9-e6ef-028f-dffa-e954207dc24d@redhat.com
next prev parent reply other threads:[~2026-01-14 10:53 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 [this message]
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
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=87h5so1n49.fsf@toke.dk \
--to=toke@kernel.org \
--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