From: Bastien Curutchet <bastien.curutchet@bootlin.com>
To: Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
Tushar Vyavahare <tushar.vyavahare@intel.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, bjorn@kernel.org,
magnus.karlsson@intel.com, jonathan.lemon@gmail.com,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
ast@kernel.org, daniel@iogearbox.net, tirthendu.sarkar@intel.com,
"Alexis Lothoré" <alexis.lothore@bootlin.com>
Subject: Re: [PATCH bpf-next v4 2/2] selftests/xsk: Add tail adjustment tests and support check
Date: Mon, 24 Mar 2025 13:32:25 +0100 [thread overview]
Message-ID: <764f5e7a-4188-4952-9122-62d5bde3bc72@bootlin.com> (raw)
In-Reply-To: <Z963wAD8HhOKdcAG@boxer>
Hi Maciej
On 3/22/25 2:14 PM, Maciej Fijalkowski wrote:
> On Fri, Mar 21, 2025 at 12:54:19AM +0000, Tushar Vyavahare wrote:
>> Introduce tail adjustment functionality in xskxceiver using
>> bpf_xdp_adjust_tail(). Add `xsk_xdp_adjust_tail` to modify packet sizes
>> and drop unmodified packets. Implement `is_adjust_tail_supported` to check
>> helper availability. Develop packet resizing tests, including shrinking
>> and growing scenarios, with functions for both single-buffer and
>> multi-buffer cases. Update the test framework to handle various scenarios
>> and adjust MTU settings. These changes enhance the testing of packet tail
>> adjustments, improving AF_XDP framework reliability.
>>
>> Signed-off-by: Tushar Vyavahare <tushar.vyavahare@intel.com>
>
> Reviewed-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
>
> We carry the description of executed tests at the beginning of
> xskxceiver.c and you have not updated it with these adjust tail tests but
> it's not a show-stopper to me. I'm okay with current state of this patch.
>
> Bastien, you probably would want to take into consideration these changes
> if they go in before your bigger work.
>
Thanks for the pointer, I'll keep an eye on it.
Best regards,
Bastien
next prev parent reply other threads:[~2025-03-24 12:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 0:54 [PATCH bpf-next v4 0/2] selftests/xsk: Add tests for XDP tail adjustment in AF_XDP Tushar Vyavahare
2025-03-21 0:54 ` [PATCH bpf-next v4 1/2] selftests/xsk: Add packet stream replacement function Tushar Vyavahare
2025-03-22 13:02 ` Maciej Fijalkowski
2025-03-21 0:54 ` [PATCH bpf-next v4 2/2] selftests/xsk: Add tail adjustment tests and support check Tushar Vyavahare
2025-03-22 13:14 ` Maciej Fijalkowski
2025-03-24 12:32 ` Bastien Curutchet [this message]
2025-04-08 16:54 ` [PATCH bpf-next v4 0/2] selftests/xsk: Add tests for XDP tail adjustment in AF_XDP Maciej Fijalkowski
2025-04-09 15:37 ` Alexei Starovoitov
-- strict thread matches above, loose matches on Subject: below --
2025-04-10 3:31 Tushar Vyavahare
2025-04-10 3:31 ` [PATCH bpf-next v4 2/2] selftests/xsk: Add tail adjustment tests and support check Tushar Vyavahare
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=764f5e7a-4188-4952-9122-62d5bde3bc72@bootlin.com \
--to=bastien.curutchet@bootlin.com \
--cc=alexis.lothore@bootlin.com \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tirthendu.sarkar@intel.com \
--cc=tushar.vyavahare@intel.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