mirror of
https://github.com/torvalds/linux.git
synced 2026-05-23 22:52:19 +02:00
309b905dee
Maintaining a modular IPv6 stack offers image size savings for specific setups, this benefit is outweighed by the architectural burden it imposes on the subsystems on implementation and maintenance. Therefore, drop it. Change CONFIG_IPV6 from tristate to bool. Remove all Kconfig dependencies across the tree that explicitly checked for IPV6=m. In addition, remove MODULE_DESCRIPTION(), MODULE_ALIAS(), MODULE_AUTHOR() and MODULE_LICENSE(). This is also replacing module_init() by device_initcall(). It is not possible to use fs_initcall() as IPv4 does because that creates a race condition on IPv6 addrconf. Finally, modify the default configs from CONFIG_IPV6=m to CONFIG_IPV6=y except for m68k as according to the bloat-o-meter the image is increasing by 330KB~ and that isn't acceptable. Instead, disable IPv6 on this architecture by default. This is aligned with m68k RAM requirements and recommendations [1]. [1] http://www.linux-m68k.org/faq/ram.html Signed-off-by: Fernando Fernandez Mancera <fmancera@suse.de> Tested-by: Ricardo B. Marlière <rbm@suse.com> Acked-by: Krzysztof Kozlowski <krzk@kernel.org> # arm64 Link: https://patch.msgid.link/20260325120928.15848-2-fmancera@suse.de Signed-off-by: Jakub Kicinski <kuba@kernel.org>
51 lines
1.8 KiB
Plaintext
51 lines
1.8 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0-only
|
|
config INFINIBAND_IPOIB
|
|
tristate "IP-over-InfiniBand"
|
|
depends on NETDEVICES && INET
|
|
help
|
|
Support for the IP-over-InfiniBand protocol (IPoIB). This
|
|
transports IP packets over InfiniBand so you can use your IB
|
|
device as a fancy NIC.
|
|
|
|
See Documentation/infiniband/ipoib.rst for more information
|
|
|
|
config INFINIBAND_IPOIB_CM
|
|
bool "IP-over-InfiniBand Connected Mode support"
|
|
depends on INFINIBAND_IPOIB
|
|
default n
|
|
help
|
|
This option enables support for IPoIB connected mode. After
|
|
enabling this option, you need to switch to connected mode
|
|
through /sys/class/net/ibXXX/mode to actually create
|
|
connections, and then increase the interface MTU with
|
|
e.g. ifconfig ib0 mtu 65520.
|
|
|
|
WARNING: Enabling connected mode will trigger some packet
|
|
drops for multicast and UD mode traffic from this interface,
|
|
unless you limit mtu for these destinations to 2044.
|
|
|
|
config INFINIBAND_IPOIB_DEBUG
|
|
bool "IP-over-InfiniBand debugging" if EXPERT
|
|
depends on INFINIBAND_IPOIB
|
|
default y
|
|
help
|
|
This option causes debugging code to be compiled into the
|
|
IPoIB driver. The output can be turned on via the
|
|
debug_level and mcast_debug_level module parameters (which
|
|
can also be set after the driver is loaded through sysfs).
|
|
|
|
This option also creates a directory tree under ipoib/ in
|
|
debugfs, which contains files that expose debugging
|
|
information about IB multicast groups used by the IPoIB
|
|
driver.
|
|
|
|
config INFINIBAND_IPOIB_DEBUG_DATA
|
|
bool "IP-over-InfiniBand data path debugging"
|
|
depends on INFINIBAND_IPOIB_DEBUG
|
|
help
|
|
This option compiles debugging code into the data path
|
|
of the IPoIB driver. The output can be turned on via the
|
|
data_debug_level module parameter; however, even with output
|
|
turned off, this debugging code will have some performance
|
|
impact.
|