From: sashiko-bot@kernel.org
To: "Bobby Eshleman" <bobbyeshleman@gmail.com>
Cc: dri-devel@lists.freedesktop.org, media-ci@linuxtv.org
Subject: Re: [PATCH net-next v7 3/3] selftests/net: devmem.py: add check_rx_large_niov
Date: Sat, 01 Aug 2026 00:33:04 +0000 [thread overview]
Message-ID: <20260801003304.D59B51F00AC4@smtp.kernel.org> (raw)
In-Reply-To: <20260730-tcpdm-large-niovs-v7-3-033d580a619d@meta.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The newly added rx_page_size probe in require_devmem() fails to execute within the correct network namespace, causing the test to incorrectly skip in containerized environments (like nk_devmem.py).
--
--- Patch [3]: [PATCH net-next v7 3/3] selftests/net: devmem.py: add check_rx_large_niov ---
commit 53558ad37aa9b0e02e2eb8a09081a53ab1fd981c
Author: Bobby Eshleman <bobbyeshleman@meta.com>
selftests/net: devmem.py: add check_rx_large_niov
Add a new devmem test case for binding the dmabuf with rx-page-size=16K.
The test sweeps RX payload sizes straddling the niov boundary to cover
the sub-niov, exact-niov, and multi-niov RX paths.
> diff --git a/tools/testing/selftests/drivers/net/hw/devmem_lib.py b/tools/testing/selftests/drivers/net/hw/devmem_lib.py
> index 0921ff03eb81c..cbe3a8e498239 100644
> --- a/tools/testing/selftests/drivers/net/hw/devmem_lib.py
> +++ b/tools/testing/selftests/drivers/net/hw/devmem_lib.py
[ ... ]
> @@ -18,6 +28,25 @@ def require_devmem(cfg):
> if not cfg.devmem_supported:
> raise KsftSkipEx("Test requires devmem support")
>
> + if rx_page_size > 0:
> + page_size = os.sysconf("SC_PAGE_SIZE")
> + if not _is_aligned(rx_page_size, page_size):
> + raise KsftSkipEx(
> + f"rx-page-size={rx_page_size} is invalid for this platform "
> + f"(must be a multiple of PAGE_SIZE={page_size})")
> +
> + if not hasattr(cfg, "devmem_rx_page_size_probed"):
> + cfg.devmem_rx_page_size_probed = {}
> +
> + if rx_page_size not in cfg.devmem_rx_page_size_probed:
> + probe_command = f"{cfg.bin_local} -f {cfg.ifname} -b {rx_page_size}"
> + cfg.devmem_rx_page_size_probed[rx_page_size] = \
> + cmd(probe_command, fail=False, shell=True).ret == 0
[Severity: Medium]
Is it intentional that this probe command executes in the default namespace
rather than the containerized network namespace?
Since cmd() is called without the ns=getattr(cfg, "netns", None) argument,
it appears this probe runs outside of the proper network context. Could this
cause tests in container environments (like nk_devmem.py) to incorrectly skip
because the rx_page_size capability probe fails?
> +
> + if not cfg.devmem_rx_page_size_probed[rx_page_size]:
> + raise KsftSkipEx(
> + f"Test requires devmem rx-page-size={rx_page_size} support")
> +
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260730-tcpdm-large-niovs-v7-0-033d580a619d@meta.com?part=3
prev parent reply other threads:[~2026-08-01 0:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 0:32 [PATCH net-next v7 0/3] net: devmem: allow rx-buf-size > PAGE_SIZE per binding Bobby Eshleman
2026-07-31 0:32 ` [PATCH net-next v7 1/3] net: devmem: allow rx-page-size > PAGE_SIZE per dmabuf binding Bobby Eshleman
2026-08-01 0:33 ` sashiko-bot
2026-07-31 0:32 ` [PATCH net-next v7 2/3] selftests/net: ncdevmem: add -b option to set rx-page-size on bind Bobby Eshleman
2026-07-31 0:32 ` [PATCH net-next v7 3/3] selftests/net: devmem.py: add check_rx_large_niov Bobby Eshleman
2026-08-01 0:33 ` 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=20260801003304.D59B51F00AC4@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bobbyeshleman@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=media-ci@linuxtv.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.