All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	pabeni@redhat.com, horms@kernel.org,
	linux-kselftest@vger.kernel.org, shuah@kernel.org,
	Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net-next v6 3/3] selftests: drv-net: convert so_txtime to drv-net
Date: Fri, 1 May 2026 17:45:41 -0700	[thread overview]
Message-ID: <20260501174541.0338ad0e@kernel.org> (raw)
In-Reply-To: <20260430132820.1944517-4-willemdebruijn.kernel@gmail.com>

On Thu, 30 Apr 2026 09:28:06 -0400 Willem de Bruijn wrote:
> From: Willem de Bruijn <willemb@google.com>
> 
> In preparation for extending to pacing hardware offload, convert the
> so_txtime.sh test to a drv-net test that can be run against netdevsim
> and real hardware.
> 
> Also update so_txtime.c to not exit on first failure, but run to
> completion and report exit code there. This helps with debugging
> unexpected results, especially when processing multiple packets,
> as happens in the "reverse_order" testcase.

Reviewed-by: Jakub Kicinski <kuba@kernel.org>

      reply	other threads:[~2026-05-02  0:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30 13:28 [PATCH net-next v6 0/3] selftests: drv-net: convert so_txtime to drv-net Willem de Bruijn
2026-04-30 13:28 ` [PATCH net-next v6 1/3] selftests: net: py: support cmd verifying expected failure Willem de Bruijn
2026-05-02  0:39   ` Jakub Kicinski
2026-05-03 22:14     ` Willem de Bruijn
2026-04-30 13:28 ` [PATCH net-next v6 2/3] selftests: net: py: add tc utility Willem de Bruijn
2026-04-30 13:28 ` [PATCH net-next v6 3/3] selftests: drv-net: convert so_txtime to drv-net Willem de Bruijn
2026-05-02  0:45   ` Jakub Kicinski [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=20260501174541.0338ad0e@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    --cc=willemb@google.com \
    --cc=willemdebruijn.kernel@gmail.com \
    /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.