From: Jakub Kicinski <kuba@kernel.org>
To: Yinjun Zhang <yinjun.zhang@corigine.com>
Cc: Jiri Pirko <jiri@resnulli.us>, Saeed Mahameed <saeed@kernel.org>,
Simon Horman <simon.horman@corigine.com>,
Leon Romanovsky <leon@kernel.org>,
David Miller <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Michael Chan <michael.chan@broadcom.com>,
Andy Gospodarek <andy@greyhouse.net>,
Gal Pressman <gal@nvidia.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Edward Cree <ecree.xilinx@gmail.com>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Andrew Lunn <andrew@lunn.ch>, Fei Qin <fei.qin@corigine.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
oss-drivers <oss-drivers@corigine.com>
Subject: Re: [PATCH/RFC net-next 1/2] devlink: expose port function commands to assign VFs to multiple netdevs
Date: Thu, 9 Feb 2023 19:30:14 -0800 [thread overview]
Message-ID: <20230209193014.3aae3f26@kernel.org> (raw)
In-Reply-To: <DM6PR13MB37058D011EC0D1CB7DD72B7BFCDE9@DM6PR13MB3705.namprd13.prod.outlook.com>
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.
next prev parent reply other threads:[~2023-02-10 3:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 15:36 [PATCH/RFC net-next 0/2] devlink: expose port function commands to assign VFs to multiple devlink Simon Horman
2023-02-06 15:36 ` [PATCH/RFC net-next 1/2] devlink: expose port function commands to assign VFs to multiple netdevs Simon Horman
2023-02-07 2:42 ` Jakub Kicinski
2023-02-08 10:38 ` Simon Horman
2023-02-08 11:21 ` Leon Romanovsky
2023-02-08 11:36 ` Simon Horman
2023-02-08 11:41 ` Jiri Pirko
2023-02-08 12:09 ` Simon Horman
2023-02-08 11:53 ` Leon Romanovsky
2023-02-08 12:05 ` Simon Horman
2023-02-08 21:37 ` Saeed Mahameed
2023-02-08 23:35 ` Jakub Kicinski
2023-02-09 0:55 ` Saeed Mahameed
2023-02-09 2:20 ` Yinjun Zhang
2023-02-09 15:15 ` Jiri Pirko
2023-02-10 2:14 ` Yinjun Zhang
2023-02-10 3:30 ` Jakub Kicinski [this message]
2023-02-10 9:45 ` Jiri Pirko
2023-02-08 11:40 ` Jiri Pirko
2023-02-08 12:07 ` Simon Horman
2023-02-08 12:34 ` Jiri Pirko
2023-02-08 12:37 ` Simon Horman
2023-02-08 23:41 ` Jakub Kicinski
2023-02-06 15:36 ` [PATCH/RFC net-next 2/2] nfp: add support for assigning VFs to different physical ports Simon Horman
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=20230209193014.3aae3f26@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=andy@greyhouse.net \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=fei.qin@corigine.com \
--cc=gal@nvidia.com \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=leon@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=saeed@kernel.org \
--cc=simon.horman@corigine.com \
--cc=vladimir.oltean@nxp.com \
--cc=yinjun.zhang@corigine.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;
as well as URLs for NNTP newsgroup(s).