[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250211162026.593b0b93@kernel.org>
Date: Tue, 11 Feb 2025 16:20:26 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: longli@...uxonhyperv.com
Cc: Jason Gunthorpe <jgg@...pe.ca>, Leon Romanovsky <leon@...nel.org>, Ajay
Sharma <sharmaajay@...rosoft.com>, Konstantin Taranov
<kotaranov@...rosoft.com>, "David S. Miller" <davem@...emloft.net>, Eric
Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
linux-rdma@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-hyperv@...r.kernel.org, Long Li
<longli@...rosoft.com>
Subject: Re: [PATCH net-next v3] hv_netvsc: Set device flags for properly
indicating bonding in Hyper-V
On Fri, 7 Feb 2025 13:55:37 -0800 longli@...uxonhyperv.com wrote:
> On Hyper-V platforms, a slave VF netdev always bonds to Netvsc and remains
> as Netvsc's only active slave as long as the slave device is present. This
> behavior is the same as a bonded device, but it's not user-configurable.
>
> Some kernel APIs (e.g those in "include/linux/netdevice.h") check for
> IFF_MASTER, IFF_SLAVE and IFF_BONDING for determing if those are used in
> a master/slave bonded setup. Netvsc's bonding setup with its slave device
> falls into this category.
Again, this is way too much of a hack. You're trying to make
netif_is_bond_master() return true for your franken-interfaces
with minimal effort.
--
pw-bot: reject
Powered by blists - more mailing lists