netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, netdev@vger.kernel.org,
	michal.swiatkowski@linux.intel.com, jiri@nvidia.com,
	shayd@nvidia.com, wojciech.drewek@intel.com, horms@kernel.org,
	sridhar.samudrala@intel.com, mateusz.polchlopek@intel.com,
	kalesh-anakkur.purayil@broadcom.com, michal.kubiak@intel.com,
	pio.raczynski@gmail.com, przemyslaw.kitszel@intel.com,
	jacob.e.keller@intel.com, maciej.fijalkowski@intel.com
Subject: Re: [PATCH net-next v4 00/15][pull request] ice: support devlink subfunction
Date: Wed, 14 Aug 2024 10:43:54 +0200	[thread overview]
Message-ID: <ZrxuSkbu7PEAmfa9@nanopsycho.orion> (raw)
In-Reply-To: <20240813215005.3647350-1-anthony.l.nguyen@intel.com>

Tue, Aug 13, 2024 at 11:49:49PM CEST, anthony.l.nguyen@intel.com wrote:
>Michal Swiatkowski says:
>
>Currently ice driver does not allow creating more than one networking
>device per physical function. The only way to have more hardware backed
>netdev is to use SR-IOV.
>
>Following patchset adds support for devlink port API. For each new
>pcisf type port, driver allocates new VSI, configures all resources
>needed, including dynamically MSIX vectors, program rules and registers
>new netdev.
>
>This series supports only one Tx/Rx queue pair per subfunction.
>
>Example commands:
>devlink port add pci/0000:31:00.1 flavour pcisf pfnum 1 sfnum 1000
>devlink port function set pci/0000:31:00.1/1 hw_addr 00:00:00:00:03:14
>devlink port function set pci/0000:31:00.1/1 state active
>devlink port function del pci/0000:31:00.1/1
>
>Make the port representor and eswitch code generic to support
>subfunction representor type.
>
>VSI configuration is slightly different between VF and SF. It needs to
>be reflected in the code.
>---
>v4:
>- fix dev warn message when index isn't supported
>- change pf->hw.bus.func to internal pf id
>- use devl_register instead of locking version
>- rephrase last commit message

Could you at least mention in which patch you do which changes?


  parent reply	other threads:[~2024-08-14  8:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-13 21:49 [PATCH net-next v4 00/15][pull request] ice: support devlink subfunction Tony Nguyen
2024-08-13 21:49 ` [PATCH net-next v4 01/15] ice: add new VSI type for subfunctions Tony Nguyen
2024-08-13 21:49 ` [PATCH net-next v4 02/15] ice: export ice ndo_ops functions Tony Nguyen
2024-08-13 21:49 ` [PATCH net-next v4 03/15] ice: add basic devlink subfunctions support Tony Nguyen
2024-08-14  8:42   ` Jiri Pirko
2024-08-14  8:54     ` Michal Swiatkowski
2024-08-14 11:55       ` Jiri Pirko
2024-08-13 21:49 ` [PATCH net-next v4 04/15] ice: treat subfunction VSI the same as PF VSI Tony Nguyen
2024-08-13 21:49 ` [PATCH net-next v4 05/15] ice: allocate devlink for subfunction Tony Nguyen
2024-08-13 21:49 ` [PATCH net-next v4 06/15] ice: base subfunction aux driver Tony Nguyen
2024-08-13 21:49 ` [PATCH net-next v4 07/15] ice: implement netdev for subfunction Tony Nguyen
2024-08-13 21:49 ` [PATCH net-next v4 08/15] ice: make representor code generic Tony Nguyen
2024-08-13 21:49 ` [PATCH net-next v4 09/15] ice: create port representor for SF Tony Nguyen
2024-08-13 21:49 ` [PATCH net-next v4 10/15] ice: don't set target VSI for subfunction Tony Nguyen
2024-08-13 21:50 ` [PATCH net-next v4 11/15] ice: check if SF is ready in ethtool ops Tony Nguyen
2024-08-13 21:50 ` [PATCH net-next v4 12/15] ice: implement netdevice ops for SF representor Tony Nguyen
2024-08-13 21:50 ` [PATCH net-next v4 13/15] ice: support subfunction devlink Tx topology Tony Nguyen
2024-08-13 21:50 ` [PATCH net-next v4 14/15] ice: basic support for VLAN in subfunctions Tony Nguyen
2024-08-13 21:50 ` [PATCH net-next v4 15/15] ice: subfunction activation and base devlink ops Tony Nguyen
2024-08-14  8:45   ` Jiri Pirko
2024-08-14  8:43 ` Jiri Pirko [this message]
2024-08-14  8:47   ` [PATCH net-next v4 00/15][pull request] ice: support devlink subfunction Michal Swiatkowski

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=ZrxuSkbu7PEAmfa9@nanopsycho.orion \
    --to=jiri@resnulli.us \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jacob.e.keller@intel.com \
    --cc=jiri@nvidia.com \
    --cc=kalesh-anakkur.purayil@broadcom.com \
    --cc=kuba@kernel.org \
    --cc=maciej.fijalkowski@intel.com \
    --cc=mateusz.polchlopek@intel.com \
    --cc=michal.kubiak@intel.com \
    --cc=michal.swiatkowski@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pio.raczynski@gmail.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=shayd@nvidia.com \
    --cc=sridhar.samudrala@intel.com \
    --cc=wojciech.drewek@intel.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).