From: Cosmin Ratiu <cratiu@nvidia.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"liuhangbin@gmail.com" <liuhangbin@gmail.com>
Cc: "andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"razor@blackwall.org" <razor@blackwall.org>,
Tariq Toukan <tariqt@nvidia.com>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"liali@redhat.com" <liali@redhat.com>,
"jv@jvosburgh.net" <jv@jvosburgh.net>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"horms@kernel.org" <horms@kernel.org>,
"edumazet@google.com" <edumazet@google.com>,
Boris Pismenny <borisp@nvidia.com>,
Jianbo Liu <jianbol@nvidia.com>,
"kuba@kernel.org" <kuba@kernel.org>
Subject: Re: [PATCHv2 net] Bonding: Fix support for gso_partial_features
Date: Thu, 23 Jan 2025 15:24:37 +0000 [thread overview]
Message-ID: <fc63c005a8f2fd6a34a055c1ac484bc36869f8a8.camel@nvidia.com> (raw)
In-Reply-To: <40707a0ed22fa87dbe6b5e28d22fad586158675e.camel@nvidia.com>
I've sent another patch to suggest these changes.
I've tested it (with iperf3 traffic) and by playing with ethtool -K on
the bond device. With simple iperf3 TCP traffic and no other tweaks, I
get 2x the performance over the bond device with my patch compared to
without.
I hope I didn't miss anything...
https://lore.kernel.org/netdev/20250123150909.387415-1-cratiu@nvidia.com/T/#u
Cosmin.
next prev parent reply other threads:[~2025-01-23 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 13:52 [PATCHv2 net] Bonding: Fix support for gso_partial_features Hangbin Liu
2025-01-23 12:15 ` Cosmin Ratiu
2025-01-23 15:24 ` Cosmin Ratiu [this message]
2025-01-24 15:38 ` Jakub Kicinski
2025-01-24 16:03 ` Cosmin Ratiu
2025-01-25 1:47 ` Jakub Kicinski
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=fc63c005a8f2fd6a34a055c1ac484bc36869f8a8.camel@nvidia.com \
--to=cratiu@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=borisp@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jianbol@nvidia.com \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=liali@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=tariqt@nvidia.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