[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <sfjjkeub7fmvsktzrx6mmv6zvilno3un665tbqe2punw4azefo@jwuhk23763gc>
Date: Tue, 14 Oct 2025 11:40:12 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: Hangbin Liu <liuhangbin@...il.com>
Cc: netdev@...r.kernel.org, Jay Vosburgh <jv@...sburgh.net>,
Andrew Lunn <andrew+netdev@...n.ch>, "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, Sabrina Dubroca <sdubroca@...hat.com>,
Simon Horman <horms@...nel.org>, Ido Schimmel <idosch@...dia.com>, Shuah Khan <shuah@...nel.org>,
Stanislav Fomichev <sdf@...ichev.me>, Stanislav Fomichev <stfomichev@...il.com>,
Kuniyuki Iwashima <kuniyu@...gle.com>, Ahmed Zaki <ahmed.zaki@...el.com>,
Alexander Lobakin <aleksander.lobakin@...el.com>, bridge@...ts.linux.dev, linux-kselftest@...r.kernel.org
Subject: Re: [PATCHv4 net-next 1/4] net: add a common function to compute
features from lowers devices
Tue, Oct 14, 2025 at 10:02:14AM +0200, liuhangbin@...il.com wrote:
[..]
>+#define VIRTUAL_DEV_VLAN_FEATURES (NETIF_F_HW_CSUM | NETIF_F_SG | \
I don't like the "virtual" naming. In the past, we always tried to avoid
that for lower-upper devices like bond/team/bridge/others. Soft-device
was the used term. Please let the "virtual" term for vitrualization,
would that be possible?
How about "master_upper"? This is already widely used to refer to
bond/team/bridge/other master soft devices.
MASTER_UPPER_DEV_VLAN_FEATURES?
[..]
>+void netdev_compute_features_from_lowers(struct net_device *dev, bool update_header)
netdev_compute_master_upper_features?
Powered by blists - more mailing lists