mirror of
https://github.com/torvalds/linux.git
synced 2026-04-25 01:52:32 -04:00
dc4305be46
The ice driver needs to write the Tx and Rx queue context when programming
Tx and Rx queues. This is currently done using some bespoke custom logic
via the ice_set_ctx() and its helper functions, along with bit position
definitions in the ice_tlan_ctx_info and ice_rlan_ctx_info structures.
This logic does work, but is problematic for several reasons:
1) ice_set_ctx requires a helper function for each byte size being packed,
as it uses a separate function to pack u8, u16, u32, and u64 fields.
This requires 4 functions which contain near-duplicate logic with the
types changed out.
2) The logic in the ice_pack_ctx_word, ice_pack_ctx_dword, and
ice_pack_ctx_qword does not handle values which straddle alignment
boundaries very well. This requires that several fields in the
ice_tlan_ctx_info and ice_rlan_ctx_info be a size larger than their bit
size should require.
3) Future support for live migration will require adding unpacking
functions to take the packed hardware context and unpack it into the
ice_rlan_ctx and ice_tlan_ctx structures. Implementing this would
require implementing ice_get_ctx, and its associated helper functions,
which essentially doubles the amount of code required.
The Linux kernel has had a packing library that can handle this logic since
commit 554aae3500 ("lib: Add support for generic packing operations").
The library was recently extended with support for packing or unpacking an
array of fields, with a similar structure as the ice_ctx_ele structure.
Replace the ice-specific ice_set_ctx() logic with the recently added
pack_fields and packed_field_s infrastructure from <linux/packing.h>
For API simplicity, the Tx and Rx queue context are programmed using
separate ice_pack_txq_ctx() and ice_pack_rxq_ctx(). This avoids needing to
export the packed_field_s arrays. The functions can pointers to the
appropriate ice_txq_ctx_buf_t and ice_rxq_ctx_buf_t types, ensuring that
only buffers of the appropriate size are passed.
Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Link: https://patch.msgid.link/20241210-packing-pack-fields-and-ice-implementation-v10-7-ee56a47479ac@intel.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
392 lines
12 KiB
Plaintext
392 lines
12 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0-only
|
|
#
|
|
# Intel network device configuration
|
|
#
|
|
|
|
config NET_VENDOR_INTEL
|
|
bool "Intel devices"
|
|
default y
|
|
help
|
|
If you have a network (Ethernet) card belonging to this class, say Y.
|
|
|
|
Note that the answer to this question doesn't directly affect the
|
|
kernel: saying N will just cause the configurator to skip all
|
|
the questions about Intel cards. If you say Y, you will be asked for
|
|
your specific card in the following questions.
|
|
|
|
if NET_VENDOR_INTEL
|
|
|
|
source "drivers/net/ethernet/intel/libeth/Kconfig"
|
|
source "drivers/net/ethernet/intel/libie/Kconfig"
|
|
|
|
config E100
|
|
tristate "Intel(R) PRO/100+ support"
|
|
depends on PCI
|
|
select MII
|
|
help
|
|
This driver supports Intel(R) PRO/100 family of adapters.
|
|
To verify that your adapter is supported, find the board ID number
|
|
on the adapter. Look for a label that has a barcode and a number
|
|
in the format 123456-001 (six digits hyphen three digits).
|
|
|
|
Use the above information and the Adapter & Driver ID Guide that
|
|
can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
to identify the adapter.
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/e100.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called e100.
|
|
|
|
config E1000
|
|
tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
|
|
depends on PCI && HAS_IOPORT
|
|
help
|
|
This driver supports Intel(R) PRO/1000 gigabit ethernet family of
|
|
adapters. For more information on how to identify your adapter, go
|
|
to the Adapter & Driver ID Guide that can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/e1000.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called e1000.
|
|
|
|
config E1000E
|
|
tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
|
|
depends on PCI && (!SPARC32 || BROKEN)
|
|
depends on PTP_1588_CLOCK_OPTIONAL
|
|
select CRC32
|
|
help
|
|
This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
|
|
ethernet family of adapters. For PCI or PCI-X e1000 adapters,
|
|
use the regular e1000 driver For more information on how to
|
|
identify your adapter, go to the Adapter & Driver ID Guide that
|
|
can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/e1000e.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called e1000e.
|
|
|
|
config E1000E_HWTS
|
|
bool "Support HW cross-timestamp on PCH devices"
|
|
default y
|
|
depends on E1000E && X86
|
|
help
|
|
Say Y to enable hardware supported cross-timestamping on PCH
|
|
devices. The cross-timestamp is available through the PTP clock
|
|
driver precise cross-timestamp ioctl (PTP_SYS_OFFSET_PRECISE).
|
|
|
|
config IGB
|
|
tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
|
|
depends on PCI
|
|
depends on PTP_1588_CLOCK_OPTIONAL
|
|
select I2C
|
|
select I2C_ALGOBIT
|
|
help
|
|
This driver supports Intel(R) 82575/82576 gigabit ethernet family of
|
|
adapters. For more information on how to identify your adapter, go
|
|
to the Adapter & Driver ID Guide that can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/igb.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called igb.
|
|
|
|
config IGB_HWMON
|
|
bool "Intel(R) PCI-Express Gigabit adapters HWMON support"
|
|
default y
|
|
depends on IGB && HWMON && !(IGB=y && HWMON=m)
|
|
help
|
|
Say Y if you want to expose thermal sensor data on Intel devices.
|
|
|
|
Some of our devices contain thermal sensors, both external and internal.
|
|
This data is available via the hwmon sysfs interface and exposes
|
|
the onboard sensors.
|
|
|
|
config IGB_DCA
|
|
bool "Direct Cache Access (DCA) Support"
|
|
default y
|
|
depends on IGB && DCA && !(IGB=y && DCA=m)
|
|
help
|
|
Say Y here if you want to use Direct Cache Access (DCA) in the
|
|
driver. DCA is a method for warming the CPU cache before data
|
|
is used, with the intent of lessening the impact of cache misses.
|
|
|
|
config IGBVF
|
|
tristate "Intel(R) 82576 Virtual Function Ethernet support"
|
|
depends on PCI
|
|
help
|
|
This driver supports Intel(R) 82576 virtual functions. For more
|
|
information on how to identify your adapter, go to the Adapter &
|
|
Driver ID Guide that can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/igbvf.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called igbvf.
|
|
|
|
config IXGBE
|
|
tristate "Intel(R) 10GbE PCI Express adapters support"
|
|
depends on PCI
|
|
depends on PTP_1588_CLOCK_OPTIONAL
|
|
select MDIO
|
|
select PHYLIB
|
|
help
|
|
This driver supports Intel(R) 10GbE PCI Express family of
|
|
adapters. For more information on how to identify your adapter, go
|
|
to the Adapter & Driver ID Guide that can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/ixgbe.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called ixgbe.
|
|
|
|
config IXGBE_HWMON
|
|
bool "Intel(R) 10GbE PCI Express adapters HWMON support"
|
|
default y
|
|
depends on IXGBE && HWMON && !(IXGBE=y && HWMON=m)
|
|
help
|
|
Say Y if you want to expose the thermal sensor data on some of
|
|
our cards, via a hwmon sysfs interface.
|
|
|
|
config IXGBE_DCA
|
|
bool "Direct Cache Access (DCA) Support"
|
|
default y
|
|
depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
|
|
help
|
|
Say Y here if you want to use Direct Cache Access (DCA) in the
|
|
driver. DCA is a method for warming the CPU cache before data
|
|
is used, with the intent of lessening the impact of cache misses.
|
|
|
|
config IXGBE_DCB
|
|
bool "Data Center Bridging (DCB) Support"
|
|
default n
|
|
depends on IXGBE && DCB
|
|
help
|
|
Say Y here if you want to use Data Center Bridging (DCB) in the
|
|
driver.
|
|
|
|
If unsure, say N.
|
|
|
|
config IXGBE_IPSEC
|
|
bool "IPSec XFRM cryptography-offload acceleration"
|
|
depends on IXGBE
|
|
depends on XFRM_OFFLOAD
|
|
default y
|
|
select XFRM_ALGO
|
|
help
|
|
Enable support for IPSec offload in ixgbe.ko
|
|
|
|
config IXGBEVF
|
|
tristate "Intel(R) 10GbE PCI Express Virtual Function Ethernet support"
|
|
depends on PCI_MSI
|
|
help
|
|
This driver supports Intel(R) PCI Express virtual functions for the
|
|
Intel(R) ixgbe driver. For more information on how to identify your
|
|
adapter, go to the Adapter & Driver ID Guide that can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/ixgbevf.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called ixgbevf. MSI-X interrupt support is required
|
|
for this driver to work correctly.
|
|
|
|
config IXGBEVF_IPSEC
|
|
bool "IPSec XFRM cryptography-offload acceleration"
|
|
depends on IXGBEVF
|
|
depends on XFRM_OFFLOAD
|
|
default y
|
|
select XFRM_ALGO
|
|
help
|
|
Enable support for IPSec offload in ixgbevf.ko
|
|
|
|
config I40E
|
|
tristate "Intel(R) Ethernet Controller XL710 Family support"
|
|
depends on PTP_1588_CLOCK_OPTIONAL
|
|
depends on PCI
|
|
select AUXILIARY_BUS
|
|
select LIBIE
|
|
select NET_DEVLINK
|
|
help
|
|
This driver supports Intel(R) Ethernet Controller XL710 Family of
|
|
devices. For more information on how to identify your adapter, go
|
|
to the Adapter & Driver ID Guide that can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/i40e.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called i40e.
|
|
|
|
config I40E_DCB
|
|
bool "Data Center Bridging (DCB) Support"
|
|
default n
|
|
depends on I40E && DCB
|
|
help
|
|
Say Y here if you want to use Data Center Bridging (DCB) in the
|
|
driver.
|
|
|
|
If unsure, say N.
|
|
|
|
# this is here to allow seamless migration from I40EVF --> IAVF name
|
|
# so that CONFIG_IAVF symbol will always mirror the state of CONFIG_I40EVF
|
|
config IAVF
|
|
tristate
|
|
select LIBIE
|
|
select NET_SHAPER
|
|
|
|
config I40EVF
|
|
tristate "Intel(R) Ethernet Adaptive Virtual Function support"
|
|
select IAVF
|
|
depends on PCI_MSI
|
|
help
|
|
This driver supports virtual functions for Intel XL710,
|
|
X710, X722, XXV710, and all devices advertising support for
|
|
Intel Ethernet Adaptive Virtual Function devices. For more
|
|
information on how to identify your adapter, go to the Adapter
|
|
& Driver ID Guide that can be located at:
|
|
|
|
<https://support.intel.com>
|
|
|
|
This driver was formerly named i40evf.
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/iavf.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called iavf. MSI-X interrupt support is required
|
|
for this driver to work correctly.
|
|
|
|
config ICE
|
|
tristate "Intel(R) Ethernet Connection E800 Series Support"
|
|
default n
|
|
depends on PCI_MSI
|
|
depends on PTP_1588_CLOCK_OPTIONAL
|
|
depends on GNSS || GNSS = n
|
|
select AUXILIARY_BUS
|
|
select DIMLIB
|
|
select LIBIE
|
|
select NET_DEVLINK
|
|
select PACKING
|
|
select PLDMFW
|
|
select DPLL
|
|
help
|
|
This driver supports Intel(R) Ethernet Connection E800 Series of
|
|
devices. For more information on how to identify your adapter, go
|
|
to the Adapter & Driver ID Guide that can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/ice.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called ice.
|
|
|
|
config ICE_HWMON
|
|
bool "Intel(R) Ethernet Connection E800 Series Support HWMON support"
|
|
default y
|
|
depends on ICE && HWMON && !(ICE=y && HWMON=m)
|
|
help
|
|
Say Y if you want to expose thermal sensor data on Intel devices.
|
|
|
|
Some of our devices contain internal thermal sensors.
|
|
This data is available via the hwmon sysfs interface and exposes
|
|
the onboard sensors.
|
|
|
|
config ICE_SWITCHDEV
|
|
bool "Switchdev Support"
|
|
default y
|
|
depends on ICE && NET_SWITCHDEV
|
|
help
|
|
Switchdev support provides internal SRIOV packet steering and switching.
|
|
|
|
To enable it on running kernel use devlink tool:
|
|
#devlink dev eswitch set pci/0000:XX:XX.X mode switchdev
|
|
|
|
Say Y here if you want to use Switchdev in the driver.
|
|
|
|
If unsure, say N.
|
|
|
|
config ICE_HWTS
|
|
bool "Support HW cross-timestamp on platforms with PTM support"
|
|
default y
|
|
depends on ICE && X86
|
|
help
|
|
Say Y to enable hardware supported cross-timestamping on platforms
|
|
with PCIe PTM support. The cross-timestamp is available through
|
|
the PTP clock driver precise cross-timestamp ioctl
|
|
(PTP_SYS_OFFSET_PRECISE).
|
|
|
|
config FM10K
|
|
tristate "Intel(R) FM10000 Ethernet Switch Host Interface Support"
|
|
default n
|
|
depends on PCI_MSI
|
|
depends on PTP_1588_CLOCK_OPTIONAL
|
|
help
|
|
This driver supports Intel(R) FM10000 Ethernet Switch Host
|
|
Interface. For more information on how to identify your adapter,
|
|
go to the Adapter & Driver ID Guide that can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/fm10k.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called fm10k. MSI-X interrupt support is required
|
|
|
|
config IGC
|
|
tristate "Intel(R) Ethernet Controller I225-LM/I225-V support"
|
|
default n
|
|
depends on PCI
|
|
depends on PTP_1588_CLOCK_OPTIONAL
|
|
help
|
|
This driver supports Intel(R) Ethernet Controller I225-LM/I225-V
|
|
family of adapters.
|
|
|
|
For more information on how to identify your adapter, go
|
|
to the Adapter & Driver ID Guide that can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called igc.
|
|
|
|
config IGC_LEDS
|
|
def_bool LEDS_TRIGGER_NETDEV
|
|
depends on IGC && LEDS_CLASS
|
|
depends on LEDS_CLASS=y || IGC=m
|
|
help
|
|
Optional support for controlling the NIC LED's with the netdev
|
|
LED trigger.
|
|
|
|
source "drivers/net/ethernet/intel/idpf/Kconfig"
|
|
|
|
endif # NET_VENDOR_INTEL
|