mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Joe Damato <jdamato@fastly.com>,  netdev@vger.kernel.org
Cc: corbet@lwn.net,  hdanton@sina.com,  bagasdotme@gmail.com,
	 pabeni@redhat.com,  namangulati@google.com,
	 edumazet@google.com,  amritha.nambiar@intel.com,
	 sridhar.samudrala@intel.com,  sdf@fomichev.me,
	 peter@typeblog.net,  m2shafiei@uwaterloo.ca,
	 bjorn@rivosinc.com,  hch@infradead.org,  willy@infradead.org,
	 willemdebruijn.kernel@gmail.com,  skhawaja@google.com,
	 kuba@kernel.org,  Joe Damato <jdamato@fastly.com>,
	 Martin Karsten <mkarsten@uwaterloo.ca>,
	 "David S. Miller" <davem@davemloft.net>,
	 Simon Horman <horms@kernel.org>,  Shuah Khan <shuah@kernel.org>,
	 linux-kernel@vger.kernel.org (open list),
	 linux-kselftest@vger.kernel.org (open list:KERNEL SELFTEST
	FRAMEWORK)
Subject: Re: [PATCH net-next v9 5/6] selftests: net: Add busy_poll_test
Date: Sat, 09 Nov 2024 10:07:18 -0500	[thread overview]
Message-ID: <672f7aa6accf5_3564c0294e3@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <20241109050245.191288-6-jdamato@fastly.com>

Joe Damato wrote:
> Add an epoll busy poll test using netdevsim.
> 
> This test is comprised of:
>   - busy_poller (via busy_poller.c)
>   - busy_poll_test.sh which loads netdevsim, sets up network namespaces,
>     and runs busy_poller to receive data and socat to send data.
> 
> The selftest tests two different scenarios:
>   - busy poll (the pre-existing version in the kernel)
>   - busy poll with suspend enabled (what this series adds)
> 
> The data transmit is a 1MiB temporary file generated from /dev/urandom
> and the test is considered passing if the md5sum of the input file to
> socat matches the md5sum of the output file from busy_poller.
> 
> netdevsim was chosen instead of veth due to netdevsim's support for
> netdev-genl.
> 
> For now, this test uses the functionality that netdevsim provides. In the
> future, perhaps netdevsim can be extended to emulate device IRQs to more
> thoroughly test all pre-existing kernel options (like defer_hard_irqs)
> and suspend.
> 
> Signed-off-by: Joe Damato <jdamato@fastly.com>
> Co-developed-by: Martin Karsten <mkarsten@uwaterloo.ca>
> Signed-off-by: Martin Karsten <mkarsten@uwaterloo.ca>
> Acked-by: Stanislav Fomichev <sdf@fomichev.me>

Reviewed-by: Willem de Bruijn <willemb@google.com>

minor nit that ULONG_MAX can not be true with uint32_t on 64-bit
platforms. Definitely no need to respin just for that.

  reply	other threads:[~2024-11-09 15:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-09  5:02 [PATCH net-next v9 0/6] Suspend IRQs during application busy periods Joe Damato
2024-11-09  5:02 ` [PATCH net-next v9 1/6] net: Add napi_struct parameter irq_suspend_timeout Joe Damato
2024-11-09  5:02 ` [PATCH net-next v9 2/6] net: Add control functions for irq suspension Joe Damato
2024-11-09  5:02 ` [PATCH net-next v9 3/6] eventpoll: Trigger napi_busy_loop, if prefer_busy_poll is set Joe Damato
2024-11-09  5:02 ` [PATCH net-next v9 4/6] eventpoll: Control irq suspension for prefer_busy_poll Joe Damato
2024-11-09  5:02 ` [PATCH net-next v9 5/6] selftests: net: Add busy_poll_test Joe Damato
2024-11-09 15:07   ` Willem de Bruijn [this message]
2025-12-19 17:05   ` Xin Long
2025-12-19 17:10     ` Xin Long
2024-11-09  5:02 ` [PATCH net-next v9 6/6] docs: networking: Describe irq suspension Joe Damato
2024-11-12  3:00 ` [PATCH net-next v9 0/6] Suspend IRQs during application busy periods 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=672f7aa6accf5_3564c0294e3@willemb.c.googlers.com.notmuch \
    --to=willemdebruijn.kernel@gmail.com \
    --cc=amritha.nambiar@intel.com \
    --cc=bagasdotme@gmail.com \
    --cc=bjorn@rivosinc.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hch@infradead.org \
    --cc=hdanton@sina.com \
    --cc=horms@kernel.org \
    --cc=jdamato@fastly.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=m2shafiei@uwaterloo.ca \
    --cc=mkarsten@uwaterloo.ca \
    --cc=namangulati@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=peter@typeblog.net \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --cc=skhawaja@google.com \
    --cc=sridhar.samudrala@intel.com \
    --cc=willy@infradead.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

all inboxes | Powered by JetHome®