Thread (22 messages) 22 messages, 3 authors, 2024-08-14

Re: [PATCH net-next v4 00/15][pull request] ice: support devlink subfunction

From: Michal Swiatkowski <hidden>
Date: 2024-08-14 08:49:16

On Wed, Aug 14, 2024 at 10:43:54AM +0200, Jiri Pirko wrote:
Tue, Aug 13, 2024 at 11:49:49PM CEST, anthony.l.nguyen@intel.com wrote:
quoted
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 
03/15
quoted
- change pf->hw.bus.func to internal pf id
03/15
quoted
- use devl_register instead of locking version
06/15
quoted
- rephrase last commit message
15/15
Could you at least mention in which patch you do which changes?
Noted.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help