All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hangbin Liu <hangbin.liu@linux.dev>
To: Ido Schimmel <idosch@idosch.org>
Cc: Ido Schimmel <idosch@nvidia.com>,
	netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	pabeni@redhat.com, edumazet@kernel.org, jv@jvosburgh.net,
	andrew+netdev@lunn.ch, razor@blackwall.org, aahila@google.com
Subject: Re: [PATCH net-next 2/2] selftests: bonding: Add a test for 802.3ad with coupled control disabled
Date: Fri, 13 Nov 2026 17:21:41 +0800	[thread overview]
Message-ID: <avbWpbswPYRV-s7H@fedora> (raw)
In-Reply-To: <20261113084240.GA3595966@shredder>

On Fri, Nov 13, 2026 at 10:42:40AM +0200, Ido Schimmel wrote:
> On Fri, Nov 13, 2026 at 03:45:25PM +0800, Hangbin Liu wrote:
> > For a pair of physically connected ports, do you mean two ports connected
> > back-to-back on the *same* host? Otherwise I’m not sure how to run the test
> > using two physical ports across two different hosts.
> 
> Yes, on the same host. That way we can test both the hardware data path
> and the software data path (with veth pairs). See
> tools/testing/selftests/net/forwarding/README 

Got it, thanks for this info.

Regards
Hangbin

  reply	other threads:[~2026-11-13  9:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 17:19 [PATCH net-next 1/2] bonding: 3ad: Receive packets in COLLECTING state Ido Schimmel
2026-11-11 17:19 ` [PATCH net-next 2/2] selftests: bonding: Add a test for 802.3ad with coupled control disabled Ido Schimmel
2026-11-12 20:21   ` netdev-bot+sashiko
2026-11-13  7:01     ` Ido Schimmel
2026-11-13  2:16   ` Hangbin Liu
2026-11-13  2:24   ` Hangbin Liu
2026-11-13  7:07     ` Ido Schimmel
2026-11-13  7:45       ` Hangbin Liu
2026-11-13  8:42         ` Ido Schimmel
2026-11-13  9:21           ` Hangbin Liu [this message]
2026-11-13  9:35   ` Nikolay Aleksandrov
2026-11-12 20:21 ` [PATCH net-next 1/2] bonding: 3ad: Receive packets in COLLECTING state netdev-bot+sashiko
2026-11-13  1:32   ` Hangbin Liu
2026-11-13  6:52   ` Ido Schimmel
2026-11-13  9:35 ` Nikolay Aleksandrov

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=avbWpbswPYRV-s7H@fedora \
    --to=hangbin.liu@linux.dev \
    --cc=aahila@google.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=idosch@idosch.org \
    --cc=idosch@nvidia.com \
    --cc=jv@jvosburgh.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=razor@blackwall.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 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.