From: Jakub Kicinski <kuba@kernel.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Haiyang Zhang <haiyangz@microsoft.com>,
Jason Wang <jasowang@redhat.com>, Cindy Lu <lulu@redhat.com>,
KY Srinivasan <kys@microsoft.com>, Wei Liu <wei.liu@kernel.org>,
Dexuan Cui <decui@microsoft.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Michael Kelley <mhklinux@outlook.com>,
Shradha Gupta <shradhagupta@linux.microsoft.com>,
Kees Cook <kees@kernel.org>, Stanislav Fomichev <sdf@fomichev.me>,
Kuniyuki Iwashima <kuniyu@google.com>,
Alexander Lobakin <aleksander.lobakin@intel.com>,
Guillaume Nault <gnault@redhat.com>,
Joe Damato <jdamato@fastly.com>,
Ahmed Zaki <ahmed.zaki@intel.com>,
"open list:Hyper-V/Azure CORE AND DRIVERS"
<linux-hyperv@vger.kernel.org>,
"open list:NETWORKING DRIVERS" <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND] netvsc: transfer lower device max tso size
Date: Mon, 28 Jul 2025 08:19:07 -0700 [thread overview]
Message-ID: <20250728081907.3de03b67@kernel.org> (raw)
In-Reply-To: <20250727200126.2682aa39@hermes.local>
On Sun, 27 Jul 2025 20:01:26 -0700 Stephen Hemminger wrote:
> On Wed, 23 Jul 2025 15:16:22 -0700
> Jakub Kicinski <kuba@kernel.org> wrote:
> >
> > > Actually, we had used the common bonding driver 9 years ago. But it's
> > > replaced by this kernel/netvsc based "transparent" bonding mode. See
> > > the patches listed below.
> > >
> > > The user mode bonding scripts were unstable, and difficult to deliver
> > > & update for various distros. So Stephen developed the new "transparent"
> > > bonding mode, which greatly improves the situation.
> >
> > I specifically highlighted systemd-networkd as the change in the user
> > space landscape.
>
> Haiyang tried valiantly but getting every distro to do the right thing
> with VF's bonding and hot plug was impossible to support.
I understand, but I also don't want it to be an upstream Linux problem.
Again, no other cloud provider seems to have this issue, AFAIU.
next prev parent reply other threads:[~2025-07-28 15:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 6:17 [PATCH RESEND] netvsc: transfer lower device max tso size Cindy Lu
2025-07-21 23:28 ` Jakub Kicinski
2025-07-22 1:04 ` Jason Wang
2025-07-22 1:18 ` Jakub Kicinski
2025-07-22 2:04 ` Cindy Lu
2025-07-22 2:46 ` Cindy Lu
2025-07-23 6:00 ` Jason Wang
2025-07-23 15:05 ` Jakub Kicinski
2025-07-23 20:18 ` Haiyang Zhang
2025-07-23 22:16 ` Jakub Kicinski
2025-07-28 3:01 ` Stephen Hemminger
2025-07-28 15:19 ` Jakub Kicinski [this message]
2025-07-28 17:24 ` Stephen Hemminger
2025-07-29 2:42 ` Jason Wang
2025-07-31 1:07 ` Jason Wang
2025-07-31 1:18 ` 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=20250728081907.3de03b67@kernel.org \
--to=kuba@kernel.org \
--cc=ahmed.zaki@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=haiyangz@microsoft.com \
--cc=horms@kernel.org \
--cc=jasowang@redhat.com \
--cc=jdamato@fastly.com \
--cc=kees@kernel.org \
--cc=kuniyu@google.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=mhklinux@outlook.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shradhagupta@linux.microsoft.com \
--cc=stephen@networkplumber.org \
--cc=wei.liu@kernel.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.