public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Dragos Tatulea <dtatulea@nvidia.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	dw@davidwei.uk, jdamato@fastly.com, asml.silence@gmail.com,
	io-uring@vger.kernel.org, shuah@kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 3/3] selftests: drv-net: iou-zcrx: allocate hugepages for large chunks test
Date: Mon, 2 Mar 2026 18:22:22 -0800	[thread overview]
Message-ID: <20260302182222.245a34d0@kernel.org> (raw)
In-Reply-To: <f827a42a-be8d-46ea-a6f8-edf0f1ee1a26@nvidia.com>

On Mon, 2 Mar 2026 16:16:38 +0100 Dragos Tatulea wrote:
> > +    hp_file = "/proc/sys/vm/nr_hugepages"
> > +    with open(hp_file, 'r+', encoding='utf-8') as f:
> > +        nr_hugepages = int(f.read().strip())
> > +        if nr_hugepages < 64:
> > +            f.seek(0)
> > +            f.write("64")
> > +            defer(lambda: open(hp_file, 'w', encoding='utf-8').write(str(nr_hugepages)))
> > +
> >      single(cfg)
> >      rx_cmd = f"{cfg.bin_local} -s -p {cfg.port} -i {cfg.ifname} -q {cfg.target} -x 2"
> >      tx_cmd = f"{cfg.bin_remote} -c -h {cfg.addr_v['6']} -p {cfg.port} -l 12840"
> >  
> >      probe = cmd(rx_cmd + " -d", fail=False)
> >      if probe.ret == SKIP_CODE:
> > -        raise KsftSkipEx(probe.stdout)
> > +        raise KsftSkipEx(probe.stdout.strip())
> >    
> While working on a similar fix I found that the probe here also requires a barrier.

Hm, I'm not hitting this issue. Maybe because I'm testing in QEMU?
If you can still repro after this series could you send a follow up?

  reply	other threads:[~2026-03-03  2:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27 17:13 [PATCH net-next 0/3] selftests: drv-net: iou-zcrx: improve stability and make the large chunk test work Jakub Kicinski
2026-02-27 17:13 ` [PATCH net-next 1/3] selftests: drv-net: iou-zcrx: wait for memory provider cleanup Jakub Kicinski
2026-03-02 15:32   ` Dragos Tatulea
2026-03-02 15:49   ` David Wei
2026-03-03  0:46     ` Jakub Kicinski
2026-03-03  1:39       ` David Wei
2026-02-27 17:13 ` [PATCH net-next 2/3] selftests: drv-net: iou-zcrx: rework large chunks test to use common setup Jakub Kicinski
2026-03-02 15:54   ` David Wei
2026-03-03  0:48     ` Jakub Kicinski
2026-03-03  1:44       ` David Wei
2026-02-27 17:13 ` [PATCH net-next 3/3] selftests: drv-net: iou-zcrx: allocate hugepages for large chunks test Jakub Kicinski
2026-03-02 15:16   ` Dragos Tatulea
2026-03-03  2:22     ` Jakub Kicinski [this message]
2026-03-03  8:41       ` Dragos Tatulea
2026-03-03  4:47 ` [PATCH net-next 0/3] selftests: drv-net: iou-zcrx: improve stability and make the large chunk test work patchwork-bot+netdevbpf

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=20260302182222.245a34d0@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=asml.silence@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dtatulea@nvidia.com \
    --cc=dw@davidwei.uk \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=io-uring@vger.kernel.org \
    --cc=jdamato@fastly.com \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    /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