From: Jakub Kicinski <kuba@kernel.org>
To: David Wei <dw@davidwei.uk>
Cc: Jiri Pirko <jiri@resnulli.us>,
Sabrina Dubroca <sd@queasysnail.net>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next v9 0/3] netdevsim: link and forward skbs between ports
Date: Fri, 9 Feb 2024 22:30:17 -0800 [thread overview]
Message-ID: <20240209223017.5a03acaf@kernel.org> (raw)
In-Reply-To: <20240210003240.847392-1-dw@davidwei.uk>
On Fri, 9 Feb 2024 16:32:37 -0800 David Wei wrote:
> This patchset adds the ability to link two netdevsim ports together and
> forward skbs between them, similar to veth. The goal is to use netdevsim
> for testing features e.g. zero copy Rx using io_uring.
>
> This feature was tested locally on QEMU, and a selftest is included.
Sadly we appear to be heading towards double-digit version numbers :)
https://netdev-3.bots.linux.dev/vmksft-netdevsim-dbg/results/458900/14-peer-sh/stdout
--
pw-bot: cr
next prev parent reply other threads:[~2024-02-10 6:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-10 0:32 [PATCH net-next v9 0/3] netdevsim: link and forward skbs between ports David Wei
2024-02-10 0:32 ` [PATCH net-next v9 1/3] netdevsim: allow two netdevsim ports to be connected David Wei
2024-02-10 0:32 ` [PATCH net-next v9 2/3] netdevsim: forward skbs from one connected port to another David Wei
2024-02-10 21:43 ` Maciek Machnikowski
2024-02-12 17:32 ` David Wei
2024-02-12 18:10 ` Maciek Machnikowski
2024-02-12 18:25 ` David Wei
2024-02-10 0:32 ` [PATCH net-next v9 3/3] netdevsim: add selftest for forwarding skb between connected ports David Wei
2024-02-10 8:48 ` Maciek Machnikowski
2024-02-10 18:53 ` Maciek Machnikowski
2024-02-12 17:20 ` David Wei
2024-02-10 6:30 ` Jakub Kicinski [this message]
2024-02-12 17:19 ` [PATCH net-next v9 0/3] netdevsim: link and forward skbs between ports David Wei
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=20240209223017.5a03acaf@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dw@davidwei.uk \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
/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;
as well as URLs for NNTP newsgroup(s).