forked from Minki/linux
a831274a13
This change replaces the network device operations for adding or removing a VXLAN port with operations that are more generically defined to be used for any UDP offload port but provide a type. As such by just adding a line to verify that the offload type is VXLAN we can maintain the same functionality. In addition I updated the socket address family check so that instead of excluding IPv6 we instead abort of type is not IPv4. This makes much more sense as we should only be supporting IPv4 outer addresses on this hardware. Signed-off-by: Alexander Duyck <aduyck@mirantis.com> Signed-off-by: David S. Miller <davem@davemloft.net>
41 lines
1.0 KiB
Plaintext
41 lines
1.0 KiB
Plaintext
#
|
|
# Mellanox driver configuration
|
|
#
|
|
|
|
config MLX4_EN
|
|
tristate "Mellanox Technologies 1/10/40Gbit Ethernet support"
|
|
depends on MAY_USE_DEVLINK
|
|
depends on PCI
|
|
select MLX4_CORE
|
|
select PTP_1588_CLOCK
|
|
---help---
|
|
This driver supports Mellanox Technologies ConnectX Ethernet
|
|
devices.
|
|
|
|
config MLX4_EN_DCB
|
|
bool "Data Center Bridging (DCB) Support"
|
|
default y
|
|
depends on MLX4_EN && DCB
|
|
---help---
|
|
Say Y here if you want to use Data Center Bridging (DCB) in the
|
|
driver.
|
|
If set to N, will not be able to configure QoS and ratelimit attributes.
|
|
This flag is depended on the kernel's DCB support.
|
|
|
|
If unsure, set to Y
|
|
|
|
config MLX4_CORE
|
|
tristate
|
|
depends on PCI
|
|
default n
|
|
|
|
config MLX4_DEBUG
|
|
bool "Verbose debugging output" if (MLX4_CORE && EXPERT)
|
|
depends on MLX4_CORE
|
|
default y
|
|
---help---
|
|
This option causes debugging code to be compiled into the
|
|
mlx4_core driver. The output can be turned on via the
|
|
debug_level module parameter (which can also be set after
|
|
the driver is loaded through sysfs).
|