From: Ido Schimmel <idosch@nvidia•com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail•com>
Cc: netdev@vger•kernel.org, davem@davemloft•net, kuba@kernel•org,
edumazet@google•com, pabeni@redhat•com, dsahern@kernel•org,
horms@kernel•org, kuniyu@amazon•com,
Willem de Bruijn <willemb@google•com>
Subject: Re: [PATCH net-next v2 3/3] selftests/net: test tcp connection load balancing
Date: Fri, 25 Apr 2025 18:47:16 +0300 [thread overview]
Message-ID: <aAuuhIYrLBNNhtJg@shredder> (raw)
In-Reply-To: <20250424143549.669426-4-willemdebruijn.kernel@gmail.com>
On Thu, Apr 24, 2025 at 10:35:20AM -0400, Willem de Bruijn wrote:
> From: Willem de Bruijn <willemb@google•com>
>
> Verify that TCP connections use both routes when connecting multiple
> times to a remote service over a two nexthop multipath route.
>
> Use socat to create the connections. Use tc prio + tc filter to
> count routes taken, counting SYN packets across the two egress
> devices. Also verify that the saddr matches that of the device.
>
> To avoid flaky tests when testing inherently randomized behavior,
> set a low bar and pass if even a single SYN is observed on each
> device.
>
> Signed-off-by: Willem de Bruijn <willemb@google•com>
Reviewed-by: Ido Schimmel <idosch@nvidia•com>
Tested-by: Ido Schimmel <idosch@nvidia•com>
>
> ---
>
> v1->v2
> - match also on saddr, not only SYN
> - move from fib_nexthops.sh to fib_tests.sh
> - move generic "count packets on dev" to lib.sh
> - switch from netcat to socat, as different netcats go around
Thanks!
next prev parent reply other threads:[~2025-04-25 15:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 14:35 [PATCH net-next v2 0/3] ip: improve tcp sock multipath routing Willem de Bruijn
2025-04-24 14:35 ` [PATCH net-next v2 1/3] ipv4: prefer multipath nexthop that matches source address Willem de Bruijn
2025-04-24 16:47 ` Eric Dumazet
2025-04-25 14:59 ` Ido Schimmel
2025-04-26 15:01 ` Willem de Bruijn
2025-04-27 17:30 ` Ido Schimmel
2025-04-28 16:26 ` Willem de Bruijn
2025-04-29 7:54 ` Ido Schimmel
2025-04-24 14:35 ` [PATCH net-next v2 2/3] ip: load balance tcp connections to single dst addr and port Willem de Bruijn
2025-04-24 16:05 ` David Ahern
2025-04-24 16:51 ` Eric Dumazet
2025-04-25 15:14 ` Ido Schimmel
2025-04-24 14:35 ` [PATCH net-next v2 3/3] selftests/net: test tcp connection load balancing Willem de Bruijn
2025-04-25 15:47 ` Ido Schimmel [this message]
2025-04-29 14:40 ` [PATCH net-next v2 0/3] ip: improve tcp sock multipath routing 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=aAuuhIYrLBNNhtJg@shredder \
--to=idosch@nvidia$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=kuniyu@amazon$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=willemb@google$(echo .)com \
--cc=willemdebruijn.kernel@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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