From: Hangbin Liu <liuhangbin@gmail.com>
To: Eric Dumazet <edumazet@google.com>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
patchwork-bot+netdevbpf@kernel.org, davem@davemloft.net,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
eric.dumazet@gmail.com, syzkaller@googlegroups.com
Subject: Re: [PATCH v2 net] wireguard: use DEV_STATS_INC()
Date: Mon, 20 Nov 2023 18:09:03 +0800 [thread overview]
Message-ID: <ZVswP0vvfCm0FlWO@Laptop-X1> (raw)
In-Reply-To: <CANn89iLm0SX4dF1Y29ui=SxO5ut=v66S6SvgFsD2cjU=JN1pmA@mail.gmail.com>
On Mon, Nov 20, 2023 at 08:56:02AM +0100, Eric Dumazet wrote:
> > I thought that, given my concerns, if this was to be committed, at
> > least Eric (or you?) would expand on the rationale in the context of
> > my concerns while (or before) doing so, rather than just applying this
> > without further discussion. As I mentioned, this is fine with me if
> > you feel strongly about it, but I would appreciate some expanded
> > explanation, just for my own understanding of the matter.
> >
> > Jason
>
> Jason, I was in week end mode, so could not reply to your message.
>
> This fix is rather obvious to me. I do not want to spend too much time on it,
> and you gave an ACK if I am not mistaken.
>
> If you prefer not letting syzbot find other bugs in wireguard (because
> hitting this issue first),
> this is fine by me. We can ask syzbot team to not include wireguard in
> their kernels.
Some performance test data may helps.
As I don't have good and same configure test machines. I just did a rough test.
Client: RHEL9.2, CPU Intel E5-2620, Memory 4096 MB, NIC I350
Server: 6.7.0-rc1, CPU Intel Xeon Silver 4216, 196608 MB, NIC I350
Before patch:
=== 4in4 TCP_STREAM: 901.05 Mbits/sec ===
=== 4in4 MPTCP_STREAM: 885.22 Mbits/sec ===
=== 4in4 UDP_STREAM: 919.91 Mbits/sec ===
=== 4in4 SCTP_STREAM: 903.12 Mbits/sec ===
After patch:
=== 4in4 TCP_STREAM: 901.07 Mbits/sec ===
=== 4in4 MPTCP_STREAM: 885.24 Mbits/sec ===
=== 4in4 UDP_STREAM: 919.91 Mbits/sec ===
=== 4in4 SCTP_STREAM: 903.14 Mbits/sec ===
Exchange the client/server role:
Before patch:
=== 4in4 TCP_STREAM: 901.08 Mbits/sec ===
=== 4in4 MPTCP_STREAM: 885.12 Mbits/sec ===
=== 4in4 UDP_STREAM: 919.94 Mbits/sec ===
=== 4in4 SCTP_STREAM: 903.09 Mbits/sec ===
After patch:
=== 4in4 TCP_STREAM: 901.04 Mbits/sec ===
=== 4in4 MPTCP_STREAM: 885.24 Mbits/sec ===
=== 4in4 UDP_STREAM: 919.91 Mbits/sec ===
=== 4in4 SCTP_STREAM: 903.11 Mbits/sec ===
The result looks good to me.
Thanks
Hangbin
prev parent reply other threads:[~2023-11-20 10:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 14:17 [PATCH v2 net] wireguard: use DEV_STATS_INC() Eric Dumazet
2023-11-17 14:28 ` Jason A. Donenfeld
2023-11-18 6:58 ` Hangbin Liu
2023-11-19 19:50 ` patchwork-bot+netdevbpf
2023-11-20 0:11 ` Jason A. Donenfeld
2023-11-20 7:56 ` Eric Dumazet
2023-11-20 8:13 ` Eric Dumazet
2023-11-20 10:09 ` Hangbin Liu [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=ZVswP0vvfCm0FlWO@Laptop-X1 \
--to=liuhangbin@gmail.com \
--cc=Jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=syzkaller@googlegroups.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 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).