From: Saeed Mahameed <saeed@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: 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, oss-drivers@corigine.com
Subject: Re: [PATCH/RFC net-next 1/2] devlink: expose port function commands to assign VFs to multiple netdevs
Date: Wed, 8 Feb 2023 16:55:12 -0800 [thread overview]
Message-ID: <Y+REcLbT6LYLJS7U@x130> (raw)
In-Reply-To: <20230208153552.4be414f6@kernel.org>
On 08 Feb 15:35, Jakub Kicinski wrote:
>On Wed, 8 Feb 2023 13:37:08 -0800 Saeed Mahameed wrote:
>> I don't understand the difference between the two modes,
>> 1) "where VFs are associated with physical ports"
>> 2) "another mode where all VFs are associated with one physical port"
>>
>> anyway here how it works for ConnectX devices, and i think the model should
>> be generalized to others as it simplifies the user life in my opinion.
>
>I'm guessing the version of the NFP Simon posted this for behaves
>much like CX3 / mlx4. One PF, multiple Ethernet ports.
Then the question is, can they do PF per port and avoid such complex APIs ?
next prev parent reply other threads:[~2023-02-09 0:55 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 [this message]
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
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=Y+REcLbT6LYLJS7U@x130 \
--to=saeed@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=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=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.