[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250423161612.3dc2923e@kernel.org>
Date: Wed, 23 Apr 2025 16:16:12 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Joe Damato <jdamato@...tly.com>
Cc: netdev@...r.kernel.org, pabeni@...hat.com, shaw.leon@...il.com, Andrew
Lunn <andrew+netdev@...n.ch>, "David S. Miller" <davem@...emloft.net>, Eric
Dumazet <edumazet@...gle.com>, Shuah Khan <shuah@...nel.org>, Alexei
Starovoitov <ast@...nel.org>, Daniel Borkmann <daniel@...earbox.net>,
Jesper Dangaard Brouer <hawk@...nel.org>, John Fastabend
<john.fastabend@...il.com>, linux-kernel@...r.kernel.org (open list),
linux-kselftest@...r.kernel.org (open list:KERNEL SELFTEST FRAMEWORK),
bpf@...r.kernel.org (open list:XDP (eXpress Data
Path):Keyword:(?:\b|_)xdp(?:\b|_))
Subject: Re: [PATCH net-next v3 3/3] selftests: drv-net: Test that NAPI ID
is non-zero
On Fri, 18 Apr 2025 01:37:05 +0000 Joe Damato wrote:
> + bin_remote = cfg.remote.deploy(cfg.test_dir / "napi_id_helper")
> + listen_cmd = f"{bin_remote} {cfg.addr_v['4']} {port}"
> +
> + with bkg(listen_cmd, ksft_wait=3) as server:
Sorry, not sure how I misread v2 but you are running the helper locally.
So you don't have to deploy it to the remote machine :(
BTW does removing the ksft_wait() from the binary work? Or does it
cause trouble? Don't think we need to wait for anything in this case.
With the XSK test we had to wait for the test to do the inspection
before we unbound. Here once we get the connection we can just exit, no?
Powered by blists - more mailing lists