All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Bobby Eshleman" <bobbyeshleman@gmail.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH net-next v5 8/8] selftests: drv-net: add netkit devmem tests
Date: Fri, 15 May 2026 17:23:16 +0000	[thread overview]
Message-ID: <20260515172317.28B7BC2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260514-tcp-dm-netkit-v5-8-408c59b91e66@meta.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The test function `check_nk_rx_hds` is missing the `@ksft_disruptive` decorator.
--

commit 6b7595d97efcd40188639cc504f84e6faae25b3e
Author: Bobby Eshleman <bobbyeshleman@meta.com>

selftests: drv-net: add netkit devmem tests

This commit adds nk_devmem.py with four tests for TCP devmem through a netkit
device. The tests duplicate the original devmem tests with adjusted parameters
for the netkit environment.

> diff --git a/tools/testing/selftests/drivers/net/hw/nk_devmem.py b/tools/testing/selftests/drivers/net/hw/nk_devmem.py
> new file mode 100755
> index 0000000000000..300ed2a70ab44
> --- /dev/null
> +++ b/tools/testing/selftests/drivers/net/hw/nk_devmem.py

[ ... ]

> +@ksft_disruptive
> +def check_nk_tx_chunks(cfg) -> None:
> +    """Run the devmem TX chunking test through netkit."""
> +    run_tx_chunks(cfg)
> +
> +
> +def check_nk_rx_hds(cfg) -> None:

Should check_nk_rx_hds() also be marked with the @ksft_disruptive decorator?

Since run_rx_hds() configures NIC hardware parameters (HDS, RSS, queue lease)
that bring the interface down and up, it appears this test will disrupt
network traffic.

Without the decorator, this function bypasses the framework's test filtering
and will run even if the user explicitly disables disruptive tests.

> +    """Run the HDS test through netkit."""
> +    run_rx_hds(cfg)
> +

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260514-tcp-dm-netkit-v5-0-408c59b91e66@meta.com?part=8

      reply	other threads:[~2026-05-15 17:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-14 17:22 [PATCH net-next v5 0/8] net: devmem: support devmem with netkit devices Bobby Eshleman
2026-05-14 17:22 ` [PATCH net-next v5 1/8] net: convert netmem_tx flag to enum Bobby Eshleman
2026-05-14 17:22 ` [PATCH net-next v5 2/8] net: netkit: declare NETMEM_TX_NO_DMA mode Bobby Eshleman
2026-05-14 17:22 ` [PATCH net-next v5 3/8] net: devmem: support TX over NETMEM_TX_NO_DMA devices Bobby Eshleman
2026-05-15 17:23   ` sashiko-bot
2026-05-14 17:22 ` [PATCH net-next v5 4/8] selftests: drv-net: ncdevmem: add -n flag to skip NIC configuration Bobby Eshleman
2026-05-14 17:22 ` [PATCH net-next v5 5/8] selftests: drv-net: make attr _nk_guest_ifname public Bobby Eshleman
2026-05-14 17:22 ` [PATCH net-next v5 6/8] selftests: drv-net: refactor devmem command builders into lib module Bobby Eshleman
2026-05-14 17:22 ` [PATCH net-next v5 7/8] selftests: drv-net: add primary_rx_redirect support to NetDrvContEnv Bobby Eshleman
2026-05-14 17:22 ` [PATCH net-next v5 8/8] selftests: drv-net: add netkit devmem tests Bobby Eshleman
2026-05-15 17:23   ` sashiko-bot [this message]

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=20260515172317.28B7BC2BCB0@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=bobbyeshleman@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.