[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230209193014.3aae3f26@kernel.org>
Date: Thu, 9 Feb 2023 19:30:14 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Yinjun Zhang <yinjun.zhang@...igine.com>
Cc: Jiri Pirko <jiri@...nulli.us>, Saeed Mahameed <saeed@...nel.org>,
Simon Horman <simon.horman@...igine.com>,
Leon Romanovsky <leon@...nel.org>,
David Miller <davem@...emloft.net>,
Paolo Abeni <pabeni@...hat.com>,
Michael Chan <michael.chan@...adcom.com>,
Andy Gospodarek <andy@...yhouse.net>,
Gal Pressman <gal@...dia.com>,
Jesse Brandeburg <jesse.brandeburg@...el.com>,
Tony Nguyen <anthony.l.nguyen@...el.com>,
Edward Cree <ecree.xilinx@...il.com>,
Vladimir Oltean <vladimir.oltean@....com>,
Andrew Lunn <andrew@...n.ch>, Fei Qin <fei.qin@...igine.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
oss-drivers <oss-drivers@...igine.com>
Subject: Re: [PATCH/RFC net-next 1/2] devlink: expose port function commands
to assign VFs to multiple netdevs
On Fri, 10 Feb 2023 02:14:27 +0000 Yinjun Zhang wrote:
> I understand in switchdev mode, the fine-grained manipulation by TC can do it.
> While legacy has fixed forwarding rule, and we hope it can be implemented without
> too much involved configuration from user if they only want legacy forwarding.
>
> As multi-port mapping to one PF NIC is scarce, maybe we should implement is as
> vendor specific configuration, make sense?
Vendor extension or not we are disallowing adding configuration
for legacy SR-IOV mode. We want people to move to switchdev mode,
otherwise we'll have to keep extending both for ever.
Powered by blists - more mailing lists