linux/include
David S. Miller a89dc58703 mlx5-updates-2023-06-09
1) Embedded CPU Virtual Functions
 2) Lightweight local SFs
 
 Daniel Jurgens says:
 ====================
 Embedded CPU Virtual Functions
 
 This series enables the creation of virtual functions on Bluefield (the
 embedded CPU platform). Embedded CPU virtual functions (EC VFs). EC VF
 creation, deletion and management interfaces are the same as those for
 virtual functions in a server with a Connect-X NIC.
 
 When using EC VFs on the ARM the creation of virtual functions on the
 host system is still supported. Host VFs eswitch vports occupy a range
 of 1..max_vfs, the EC VF vport range is max_vfs+1..max_ec_vfs.
 
 Every function (PF, ECPF, VF, EC VF, and subfunction) has a function ID
 associated with it. Prior to this series the function ID and the eswitch
 vport were the same. That is no longer the case, the EC VF function ID
 range is 1..max_ec_vfs. When querying or setting the capabilities of an
 EC VF function an new bit must be set in the query/set HCA cap
 structure.
 
 This is a high level overview of the changes made:
 	- Allocate vports for EC VFs if they are enabled.
 	- Create representors and devlink ports for the EC VF vports.
 	- When querying/setting HCA caps by vport break the assumption
 	  that function ID is the same a vport number and adjust
 	  accordingly.
 	- Create a new type of page, so that when SRIOV on the ARM is
 	  disabled, but remains enabled on the host, the driver can
 	  wait for the correct pages.
 	- Update SRIOV code to support EC VF creation/deletion.
 
 ===================
 
 Lightweight local SFs:
 
 Last 3 patches form Shay Drory:
 
 SFs are heavy weight and by default they come with the full package of
 ConnectX features. Usually users want specialized SFs for one specific
 purpose and using devlink users will almost always override the set of
 advertises features of an SF and reload it.
 
 Shay Drory says:
 ================
 In order to avoid the wasted time and resources on the reload, local SFs
 will probe without any auxiliary sub-device, so that the SFs can be
 configured prior to its full probe.
 
 The defaults of the enable_* devlink params of these SFs are set to
 false.
 
 Usage example:
 Create SF:
 $ devlink port add pci/0000:08:00.0 flavour pcisf pfnum 0 sfnum 11
 $ devlink port function set pci/0000:08:00.0/32768 \
                hw_addr 00:00:00:00:00:11 state active
 
 Enable ETH auxiliary device:
 $ devlink dev param set auxiliary/mlx5_core.sf.1 \
               name enable_eth value true cmode driverinit
 
 Now, in order to fully probe the SF, use devlink reload:
 $ devlink dev reload auxiliary/mlx5_core.sf.1
 
 At this point the user have SF devlink instance with auxiliary device
 for the Ethernet functionality only.
 
 ================
 -----BEGIN PGP SIGNATURE-----
 
 iQEzBAABCAAdFiEEGhZs6bAKwk/OTgTpSD+KveBX+j4FAmSD1KUACgkQSD+KveBX
 +j5JMwf/SGo0DwXm0GTu+RlUmoUpCYG40QjJwNwJ9WUNIB/zMpnGrx59dtdhuVUb
 3gD8T9MVT08NXjQIzQReAZu9hm9MvM6jvTnUG++fFyjjlHuI/9hXWBgz1aSPcQOC
 ZR2ZHuFZsTTRWNe3JU5v9tuHOE0c6xZBAzPdDU3Lib0LvhIbZGK2eiSb11RIGU3V
 FTUskLUPMo5ObUNS55lgcTFquK90Qy41LUv0DX3MpbOY/YnDBiycikopwDoYtYQ6
 9/kOM+VOprW+BgalLyGHJ77BDg7O/k1ZxnL6J7mGn7tAhOkKX5+06xGfZnEifI2F
 nTuXYI5O8TDBdZYpmO+sBOh+SVyUrg==
 =H9kD
 -----END PGP SIGNATURE-----

Merge tag 'mlx5-updates-2023-06-09' of git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux

mlx5-updates-2023-06-09

1) Embedded CPU Virtual Functions
2) Lightweight local SFs

Daniel Jurgens says:
====================
Embedded CPU Virtual Functions

This series enables the creation of virtual functions on Bluefield (the
embedded CPU platform). Embedded CPU virtual functions (EC VFs). EC VF
creation, deletion and management interfaces are the same as those for
virtual functions in a server with a Connect-X NIC.

When using EC VFs on the ARM the creation of virtual functions on the
host system is still supported. Host VFs eswitch vports occupy a range
of 1..max_vfs, the EC VF vport range is max_vfs+1..max_ec_vfs.

Every function (PF, ECPF, VF, EC VF, and subfunction) has a function ID
associated with it. Prior to this series the function ID and the eswitch
vport were the same. That is no longer the case, the EC VF function ID
range is 1..max_ec_vfs. When querying or setting the capabilities of an
EC VF function an new bit must be set in the query/set HCA cap
structure.

This is a high level overview of the changes made:
	- Allocate vports for EC VFs if they are enabled.
	- Create representors and devlink ports for the EC VF vports.
	- When querying/setting HCA caps by vport break the assumption
	  that function ID is the same a vport number and adjust
	  accordingly.
	- Create a new type of page, so that when SRIOV on the ARM is
	  disabled, but remains enabled on the host, the driver can
	  wait for the correct pages.
	- Update SRIOV code to support EC VF creation/deletion.

===================

Lightweight local SFs:

Last 3 patches form Shay Drory:

SFs are heavy weight and by default they come with the full package of
ConnectX features. Usually users want specialized SFs for one specific
purpose and using devlink users will almost always override the set of
advertises features of an SF and reload it.

Shay Drory says:
================
In order to avoid the wasted time and resources on the reload, local SFs
will probe without any auxiliary sub-device, so that the SFs can be
configured prior to its full probe.

The defaults of the enable_* devlink params of these SFs are set to
false.

Usage example:
Create SF:
$ devlink port add pci/0000:08:00.0 flavour pcisf pfnum 0 sfnum 11
$ devlink port function set pci/0000:08:00.0/32768 \
               hw_addr 00:00:00:00:00:11 state active

Enable ETH auxiliary device:
$ devlink dev param set auxiliary/mlx5_core.sf.1 \
              name enable_eth value true cmode driverinit

Now, in order to fully probe the SF, use devlink reload:
$ devlink dev reload auxiliary/mlx5_core.sf.1

At this point the user have SF devlink instance with auxiliary device
for the Ethernet functionality only.

================
2023-06-12 11:41:57 +01:00
..
acpi Power management updates for 6.4-rc1 2023-04-25 18:44:10 -07:00
asm-generic vmlinux.lds.h: Discard .note.gnu.property section 2023-05-16 06:30:50 -07:00
clocksource
crypto crypto: af_alg: Use extract_iter_to_sg() to create scatterlists 2023-06-08 13:42:34 +02:00
drm drm: fix drmm_mutex_init() 2023-05-22 12:23:50 +02:00
dt-bindings - mailbox api: allow direct registration to a channel 2023-05-07 10:17:33 -07:00
keys
kunit
kvm s390: 2023-05-01 12:06:20 -07:00
linux mlx5-updates-2023-06-09 2023-06-12 11:41:57 +01:00
math-emu
media media: v4l2-subdev: Fix missing kerneldoc for client_caps 2023-06-02 18:46:09 +01:00
memory
misc
net tcp: remove size parameter from tcp_stream_alloc_skb() 2023-06-12 11:38:54 +01:00
pcmcia
ras
rdma
rv
scsi Driver core changes for 6.4-rc1 2023-04-27 11:53:57 -07:00
soc Nothing looks out of the ordinary in this batch of clk driver updates. There 2023-04-29 17:29:39 -07:00
sound ASoC: Intel: avs: Account for UID of ACPI device 2023-05-22 11:18:24 +01:00
target scsi: target: iscsi: Remove unused transport_timer 2023-05-22 16:29:39 -04:00
trace NFSD 6.4 Release Notes 2023-04-29 11:04:14 -07:00
uapi net: core: add getsockopt SO_PEERPIDFD 2023-06-12 10:45:50 +01:00
ufs scsi: ufs: core: Rename symbol sizeof_utp_transfer_cmd_desc() 2023-05-16 21:07:26 -04:00
vdso
video
xen