From: Yinjun Zhang <yinjun.zhang@corigine.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: Saeed Mahameed <saeed@kernel.org>,
Jakub Kicinski <kuba@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: Fri, 10 Feb 2023 02:14:27 +0000 [thread overview]
Message-ID: <DM6PR13MB37058D011EC0D1CB7DD72B7BFCDE9@DM6PR13MB3705.namprd13.prod.outlook.com> (raw)
In-Reply-To: <Y+UOLkAWD0yCJHCb@nanopsycho>
On Thu, 9 Feb 2023 16:15:58 +0100, Jiri Pirko wrote:
> Thu, Feb 09, 2023 at 03:20:48AM CET, yinjun.zhang@corigine.com wrote:
> >
> >Let me take NFP implementation for example here, all the VFs created from the single PF
> >use p0 as the uplink port by default. In legacy mode, by no means we can choose other
>
> Legacy is legacy. I believe it is like 5 years already no knobs for
> legacy mode are accepted. You should not use it for new features.
> Why this is any different?
>
> Implement TC offloading and then you can ballance the hell out of the
> thing :)
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?
>
>
> >ports as outlet. So what we're doing here is try to simulate one-port-per-PF case, to split
> >one switch-set to several switch-sets with every physical port as the uplink port respectively,
> >by grouping the VFs and assigning them to physical ports.
next prev parent reply other threads:[~2023-02-10 2:14 UTC|newest]
Thread overview: 25+ 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 [this message]
2023-02-10 3:30 ` Jakub Kicinski
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-13 3:00 ` kernel test robot
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=DM6PR13MB37058D011EC0D1CB7DD72B7BFCDE9@DM6PR13MB3705.namprd13.prod.outlook.com \
--to=yinjun.zhang@corigine.com \
--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=kuba@kernel.org \
--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 \
/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.