1 # SPDX-License-Identifier: GPL-2.0-only 1 # SPDX-License-Identifier: GPL-2.0-only
2 # 2 #
3 # Network configuration 3 # Network configuration
4 # 4 #
5 5
6 menuconfig NET 6 menuconfig NET
7 bool "Networking support" 7 bool "Networking support"
8 select NLATTR 8 select NLATTR
9 select GENERIC_NET_UTILS 9 select GENERIC_NET_UTILS
10 select BPF 10 select BPF
11 help 11 help
12 Unless you really know what you are 12 Unless you really know what you are doing, you should say Y here.
13 The reason is that some programs nee 13 The reason is that some programs need kernel networking support even
14 when running on a stand-alone machin 14 when running on a stand-alone machine that isn't connected to any
15 other computer. 15 other computer.
16 16
17 If you are upgrading from an older k 17 If you are upgrading from an older kernel, you
18 should consider updating your networ 18 should consider updating your networking tools too because changes
19 in the kernel and the tools often go 19 in the kernel and the tools often go hand in hand. The tools are
20 contained in the package net-tools, 20 contained in the package net-tools, the location and version number
21 of which are given in <file:Document 21 of which are given in <file:Documentation/Changes>.
22 22
23 For a general introduction to Linux 23 For a general introduction to Linux networking, it is highly
24 recommended to read the NET-HOWTO, a 24 recommended to read the NET-HOWTO, available from
25 <http://www.tldp.org/docs.html#howto 25 <http://www.tldp.org/docs.html#howto>.
26 26
27 if NET 27 if NET
28 28
29 config WANT_COMPAT_NETLINK_MESSAGES 29 config WANT_COMPAT_NETLINK_MESSAGES
30 bool 30 bool
31 help 31 help
32 This option can be selected by other 32 This option can be selected by other options that need compat
33 netlink messages. 33 netlink messages.
34 34
35 config COMPAT_NETLINK_MESSAGES 35 config COMPAT_NETLINK_MESSAGES
36 def_bool y 36 def_bool y
37 depends on COMPAT 37 depends on COMPAT
38 depends on WEXT_CORE || WANT_COMPAT_NE 38 depends on WEXT_CORE || WANT_COMPAT_NETLINK_MESSAGES
39 help 39 help
40 This option makes it possible to sen 40 This option makes it possible to send different netlink messages
41 to tasks depending on whether the ta 41 to tasks depending on whether the task is a compat task or not. To
42 achieve this, you need to set skb_sh 42 achieve this, you need to set skb_shinfo(skb)->frag_list to the
43 compat skb before sending the skb, t 43 compat skb before sending the skb, the netlink code will sort out
44 which message to actually pass to th 44 which message to actually pass to the task.
45 45
46 Newly written code should NEVER need 46 Newly written code should NEVER need this option but do
47 compat-independent messages instead! 47 compat-independent messages instead!
48 48
49 config NET_INGRESS 49 config NET_INGRESS
50 bool 50 bool
51 51
52 config NET_EGRESS 52 config NET_EGRESS
53 bool 53 bool
54 54
55 config NET_XGRESS 55 config NET_XGRESS
56 select NET_INGRESS 56 select NET_INGRESS
57 select NET_EGRESS 57 select NET_EGRESS
58 bool 58 bool
59 59
60 config NET_REDIRECT 60 config NET_REDIRECT
61 bool 61 bool
62 62
63 config SKB_DECRYPTED <<
64 bool <<
65 <<
66 config SKB_EXTENSIONS 63 config SKB_EXTENSIONS
67 bool 64 bool
68 65
69 config NET_DEVMEM <<
70 def_bool y <<
71 depends on DMA_SHARED_BUFFER <<
72 depends on GENERIC_ALLOCATOR <<
73 depends on PAGE_POOL <<
74 <<
75 menu "Networking options" 66 menu "Networking options"
76 67
77 source "net/packet/Kconfig" 68 source "net/packet/Kconfig"
78 source "net/unix/Kconfig" 69 source "net/unix/Kconfig"
79 source "net/tls/Kconfig" 70 source "net/tls/Kconfig"
80 source "net/xfrm/Kconfig" 71 source "net/xfrm/Kconfig"
81 source "net/iucv/Kconfig" 72 source "net/iucv/Kconfig"
82 source "net/smc/Kconfig" 73 source "net/smc/Kconfig"
83 source "net/xdp/Kconfig" 74 source "net/xdp/Kconfig"
84 75
85 config NET_HANDSHAKE 76 config NET_HANDSHAKE
86 bool 77 bool
87 depends on SUNRPC || NVME_TARGET_TCP | 78 depends on SUNRPC || NVME_TARGET_TCP || NVME_TCP
88 default y 79 default y
89 80
90 config NET_HANDSHAKE_KUNIT_TEST 81 config NET_HANDSHAKE_KUNIT_TEST
91 tristate "KUnit tests for the handshak 82 tristate "KUnit tests for the handshake upcall mechanism" if !KUNIT_ALL_TESTS
92 default KUNIT_ALL_TESTS 83 default KUNIT_ALL_TESTS
93 depends on KUNIT 84 depends on KUNIT
94 help 85 help
95 This builds the KUnit tests for the 86 This builds the KUnit tests for the handshake upcall mechanism.
96 87
97 KUnit tests run during boot and outp 88 KUnit tests run during boot and output the results to the debug
98 log in TAP format (https://testanyth 89 log in TAP format (https://testanything.org/). Only useful for
99 kernel devs running KUnit test harne 90 kernel devs running KUnit test harness and are not for inclusion
100 into a production build. 91 into a production build.
101 92
102 For more information on KUnit and un 93 For more information on KUnit and unit tests in general, refer
103 to the KUnit documentation in Docume 94 to the KUnit documentation in Documentation/dev-tools/kunit/.
104 95
105 config INET 96 config INET
106 bool "TCP/IP networking" 97 bool "TCP/IP networking"
107 help 98 help
108 These are the protocols used on the 99 These are the protocols used on the Internet and on most local
109 Ethernets. It is highly recommended 100 Ethernets. It is highly recommended to say Y here (this will enlarge
110 your kernel by about 400 KB), since 101 your kernel by about 400 KB), since some programs (e.g. the X window
111 system) use TCP/IP even if your mach 102 system) use TCP/IP even if your machine is not connected to any
112 other computer. You will get the so- 103 other computer. You will get the so-called loopback device which
113 allows you to ping yourself (great f 104 allows you to ping yourself (great fun, that!).
114 105
115 For an excellent introduction to Lin 106 For an excellent introduction to Linux networking, please read the
116 Linux Networking HOWTO, available fr 107 Linux Networking HOWTO, available from
117 <http://www.tldp.org/docs.html#howto 108 <http://www.tldp.org/docs.html#howto>.
118 109
119 If you say Y here and also to "/proc 110 If you say Y here and also to "/proc file system support" and
120 "Sysctl support" below, you can chan 111 "Sysctl support" below, you can change various aspects of the
121 behavior of the TCP/IP code by writi 112 behavior of the TCP/IP code by writing to the (virtual) files in
122 /proc/sys/net/ipv4/*; the options ar 113 /proc/sys/net/ipv4/*; the options are explained in the file
123 <file:Documentation/networking/ip-sy 114 <file:Documentation/networking/ip-sysctl.rst>.
124 115
125 Short answer: say Y. 116 Short answer: say Y.
126 117
127 if INET 118 if INET
128 source "net/ipv4/Kconfig" 119 source "net/ipv4/Kconfig"
129 source "net/ipv6/Kconfig" 120 source "net/ipv6/Kconfig"
130 source "net/netlabel/Kconfig" 121 source "net/netlabel/Kconfig"
131 source "net/mptcp/Kconfig" 122 source "net/mptcp/Kconfig"
132 123
133 endif # if INET 124 endif # if INET
134 125
135 config NETWORK_SECMARK 126 config NETWORK_SECMARK
136 bool "Security Marking" 127 bool "Security Marking"
137 help 128 help
138 This enables security marking of net 129 This enables security marking of network packets, similar
139 to nfmark, but designated for securi 130 to nfmark, but designated for security purposes.
140 If you are unsure how to answer this 131 If you are unsure how to answer this question, answer N.
141 132
142 config NET_PTP_CLASSIFY 133 config NET_PTP_CLASSIFY
143 def_bool n 134 def_bool n
144 135
145 config NETWORK_PHY_TIMESTAMPING 136 config NETWORK_PHY_TIMESTAMPING
146 bool "Timestamping in PHY devices" 137 bool "Timestamping in PHY devices"
147 select NET_PTP_CLASSIFY 138 select NET_PTP_CLASSIFY
148 help 139 help
149 This allows timestamping of network 140 This allows timestamping of network packets by PHYs (or
150 other MII bus snooping devices) with 141 other MII bus snooping devices) with hardware timestamping
151 capabilities. This option adds some 142 capabilities. This option adds some overhead in the transmit
152 and receive paths. 143 and receive paths.
153 144
154 If you are unsure how to answer this 145 If you are unsure how to answer this question, answer N.
155 146
156 menuconfig NETFILTER 147 menuconfig NETFILTER
157 bool "Network packet filtering framewo 148 bool "Network packet filtering framework (Netfilter)"
158 help 149 help
159 Netfilter is a framework for filteri 150 Netfilter is a framework for filtering and mangling network packets
160 that pass through your Linux box. 151 that pass through your Linux box.
161 152
162 The most common use of packet filter 153 The most common use of packet filtering is to run your Linux box as
163 a firewall protecting a local networ 154 a firewall protecting a local network from the Internet. The type of
164 firewall provided by this kernel sup 155 firewall provided by this kernel support is called a "packet
165 filter", which means that it can rej 156 filter", which means that it can reject individual network packets
166 based on type, source, destination e 157 based on type, source, destination etc. The other kind of firewall,
167 a "proxy-based" one, is more secure 158 a "proxy-based" one, is more secure but more intrusive and more
168 bothersome to set up; it inspects th 159 bothersome to set up; it inspects the network traffic much more
169 closely, modifies it and has knowled 160 closely, modifies it and has knowledge about the higher level
170 protocols, which a packet filter lac 161 protocols, which a packet filter lacks. Moreover, proxy-based
171 firewalls often require changes to t 162 firewalls often require changes to the programs running on the local
172 clients. Proxy-based firewalls don't 163 clients. Proxy-based firewalls don't need support by the kernel, but
173 they are often combined with a packe 164 they are often combined with a packet filter, which only works if
174 you say Y here. 165 you say Y here.
175 166
176 You should also say Y here if you in 167 You should also say Y here if you intend to use your Linux box as
177 the gateway to the Internet for a lo 168 the gateway to the Internet for a local network of machines without
178 globally valid IP addresses. This is 169 globally valid IP addresses. This is called "masquerading": if one
179 of the computers on your local netwo 170 of the computers on your local network wants to send something to
180 the outside, your box can "masquerad 171 the outside, your box can "masquerade" as that computer, i.e. it
181 forwards the traffic to the intended 172 forwards the traffic to the intended outside destination, but
182 modifies the packets to make it look 173 modifies the packets to make it look like they came from the
183 firewall box itself. It works both w 174 firewall box itself. It works both ways: if the outside host
184 replies, the Linux box will silently 175 replies, the Linux box will silently forward the traffic to the
185 correct local computer. This way, th 176 correct local computer. This way, the computers on your local net
186 are completely invisible to the outs 177 are completely invisible to the outside world, even though they can
187 reach the outside and can receive re 178 reach the outside and can receive replies. It is even possible to
188 run globally visible servers from wi 179 run globally visible servers from within a masqueraded local network
189 using a mechanism called portforward 180 using a mechanism called portforwarding. Masquerading is also often
190 called NAT (Network Address Translat 181 called NAT (Network Address Translation).
191 182
192 Another use of Netfilter is in trans 183 Another use of Netfilter is in transparent proxying: if a machine on
193 the local network tries to connect t 184 the local network tries to connect to an outside host, your Linux
194 box can transparently forward the tr 185 box can transparently forward the traffic to a local server,
195 typically a caching proxy server. 186 typically a caching proxy server.
196 187
197 Yet another use of Netfilter is buil 188 Yet another use of Netfilter is building a bridging firewall. Using
198 a bridge with Network packet filteri 189 a bridge with Network packet filtering enabled makes iptables "see"
199 the bridged traffic. For filtering o 190 the bridged traffic. For filtering on the lower network and Ethernet
200 protocols over the bridge, use ebtab 191 protocols over the bridge, use ebtables (under bridge netfilter
201 configuration). 192 configuration).
202 193
203 Various modules exist for netfilter 194 Various modules exist for netfilter which replace the previous
204 masquerading (ipmasqadm), packet fil 195 masquerading (ipmasqadm), packet filtering (ipchains), transparent
205 proxying, and portforwarding mechani 196 proxying, and portforwarding mechanisms. Please see
206 <file:Documentation/Changes> under " 197 <file:Documentation/Changes> under "iptables" for the location of
207 these packages. 198 these packages.
208 199
209 if NETFILTER 200 if NETFILTER
210 201
211 config NETFILTER_ADVANCED 202 config NETFILTER_ADVANCED
212 bool "Advanced netfilter configuration 203 bool "Advanced netfilter configuration"
213 depends on NETFILTER 204 depends on NETFILTER
214 default y 205 default y
215 help 206 help
216 If you say Y here you can select bet 207 If you say Y here you can select between all the netfilter modules.
217 If you say N the more unusual ones w 208 If you say N the more unusual ones will not be shown and the
218 basic ones needed by most people wil 209 basic ones needed by most people will default to 'M'.
219 210
220 If unsure, say Y. 211 If unsure, say Y.
221 212
222 config BRIDGE_NETFILTER 213 config BRIDGE_NETFILTER
223 tristate "Bridged IP/ARP packets filte 214 tristate "Bridged IP/ARP packets filtering"
224 depends on BRIDGE 215 depends on BRIDGE
225 depends on NETFILTER && INET 216 depends on NETFILTER && INET
226 depends on NETFILTER_ADVANCED 217 depends on NETFILTER_ADVANCED
227 select NETFILTER_FAMILY_BRIDGE 218 select NETFILTER_FAMILY_BRIDGE
228 select SKB_EXTENSIONS 219 select SKB_EXTENSIONS
229 help 220 help
230 Enabling this option will let arptab 221 Enabling this option will let arptables resp. iptables see bridged
231 ARP resp. IP traffic. If you want a 222 ARP resp. IP traffic. If you want a bridging firewall, you probably
232 want this option enabled. 223 want this option enabled.
233 Enabling or disabling this option do 224 Enabling or disabling this option doesn't enable or disable
234 ebtables. 225 ebtables.
235 226
236 If unsure, say N. 227 If unsure, say N.
237 228
238 source "net/netfilter/Kconfig" 229 source "net/netfilter/Kconfig"
239 source "net/ipv4/netfilter/Kconfig" 230 source "net/ipv4/netfilter/Kconfig"
240 source "net/ipv6/netfilter/Kconfig" 231 source "net/ipv6/netfilter/Kconfig"
241 source "net/bridge/netfilter/Kconfig" 232 source "net/bridge/netfilter/Kconfig"
242 233
243 endif 234 endif
244 235
245 source "net/dccp/Kconfig" 236 source "net/dccp/Kconfig"
246 source "net/sctp/Kconfig" 237 source "net/sctp/Kconfig"
247 source "net/rds/Kconfig" 238 source "net/rds/Kconfig"
248 source "net/tipc/Kconfig" 239 source "net/tipc/Kconfig"
249 source "net/atm/Kconfig" 240 source "net/atm/Kconfig"
250 source "net/l2tp/Kconfig" 241 source "net/l2tp/Kconfig"
251 source "net/802/Kconfig" 242 source "net/802/Kconfig"
252 source "net/bridge/Kconfig" 243 source "net/bridge/Kconfig"
253 source "net/dsa/Kconfig" 244 source "net/dsa/Kconfig"
254 source "net/8021q/Kconfig" 245 source "net/8021q/Kconfig"
255 source "net/llc/Kconfig" 246 source "net/llc/Kconfig"
256 source "net/appletalk/Kconfig" 247 source "net/appletalk/Kconfig"
257 source "net/x25/Kconfig" 248 source "net/x25/Kconfig"
258 source "net/lapb/Kconfig" 249 source "net/lapb/Kconfig"
259 source "net/phonet/Kconfig" 250 source "net/phonet/Kconfig"
260 source "net/6lowpan/Kconfig" 251 source "net/6lowpan/Kconfig"
261 source "net/ieee802154/Kconfig" 252 source "net/ieee802154/Kconfig"
262 source "net/mac802154/Kconfig" 253 source "net/mac802154/Kconfig"
263 source "net/sched/Kconfig" 254 source "net/sched/Kconfig"
264 source "net/dcb/Kconfig" 255 source "net/dcb/Kconfig"
265 source "net/dns_resolver/Kconfig" 256 source "net/dns_resolver/Kconfig"
266 source "net/batman-adv/Kconfig" 257 source "net/batman-adv/Kconfig"
267 source "net/openvswitch/Kconfig" 258 source "net/openvswitch/Kconfig"
268 source "net/vmw_vsock/Kconfig" 259 source "net/vmw_vsock/Kconfig"
269 source "net/netlink/Kconfig" 260 source "net/netlink/Kconfig"
270 source "net/mpls/Kconfig" 261 source "net/mpls/Kconfig"
271 source "net/nsh/Kconfig" 262 source "net/nsh/Kconfig"
272 source "net/hsr/Kconfig" 263 source "net/hsr/Kconfig"
273 source "net/switchdev/Kconfig" 264 source "net/switchdev/Kconfig"
274 source "net/l3mdev/Kconfig" 265 source "net/l3mdev/Kconfig"
275 source "net/qrtr/Kconfig" 266 source "net/qrtr/Kconfig"
276 source "net/ncsi/Kconfig" 267 source "net/ncsi/Kconfig"
277 268
278 config PCPU_DEV_REFCNT 269 config PCPU_DEV_REFCNT
279 bool "Use percpu variables to maintain 270 bool "Use percpu variables to maintain network device refcount"
280 depends on SMP 271 depends on SMP
281 default y 272 default y
282 help 273 help
283 network device refcount are using pe 274 network device refcount are using per cpu variables if this option is set.
284 This can be forced to N to detect un 275 This can be forced to N to detect underflows (with a performance drop).
285 276
286 config MAX_SKB_FRAGS 277 config MAX_SKB_FRAGS
287 int "Maximum number of fragments per s 278 int "Maximum number of fragments per skb_shared_info"
288 range 17 45 279 range 17 45
289 default 17 280 default 17
290 help 281 help
291 Having more fragments per skb_shared 282 Having more fragments per skb_shared_info can help GRO efficiency.
292 This helps BIG TCP workloads, but mi 283 This helps BIG TCP workloads, but might expose bugs in some
293 legacy drivers. 284 legacy drivers.
294 This also increases memory overhead 285 This also increases memory overhead of small packets,
295 and in drivers using build_skb(). 286 and in drivers using build_skb().
296 If unsure, say 17. 287 If unsure, say 17.
297 288
298 config RPS 289 config RPS
299 bool "Receive packet steering" !! 290 bool
300 depends on SMP && SYSFS 291 depends on SMP && SYSFS
301 default y 292 default y
302 help <<
303 Software receive side packet steerin <<
304 load of received packet processing a <<
305 293
306 config RFS_ACCEL 294 config RFS_ACCEL
307 bool "Hardware acceleration of RFS" !! 295 bool
308 depends on RPS 296 depends on RPS
309 select CPU_RMAP 297 select CPU_RMAP
310 default y 298 default y
311 help <<
312 Allowing drivers for multiqueue hard <<
313 accelerate RFS. <<
314 299
315 config SOCK_RX_QUEUE_MAPPING 300 config SOCK_RX_QUEUE_MAPPING
316 bool 301 bool
317 302
318 config XPS 303 config XPS
319 bool 304 bool
320 depends on SMP 305 depends on SMP
321 select SOCK_RX_QUEUE_MAPPING 306 select SOCK_RX_QUEUE_MAPPING
322 default y 307 default y
323 308
324 config HWBM 309 config HWBM
325 bool 310 bool
326 311
327 config CGROUP_NET_PRIO 312 config CGROUP_NET_PRIO
328 bool "Network priority cgroup" 313 bool "Network priority cgroup"
329 depends on CGROUPS 314 depends on CGROUPS
330 select SOCK_CGROUP_DATA 315 select SOCK_CGROUP_DATA
331 help 316 help
332 Cgroup subsystem for use in assignin 317 Cgroup subsystem for use in assigning processes to network priorities on
333 a per-interface basis. 318 a per-interface basis.
334 319
335 config CGROUP_NET_CLASSID 320 config CGROUP_NET_CLASSID
336 bool "Network classid cgroup" 321 bool "Network classid cgroup"
337 depends on CGROUPS 322 depends on CGROUPS
338 select SOCK_CGROUP_DATA 323 select SOCK_CGROUP_DATA
339 help 324 help
340 Cgroup subsystem for use as general 325 Cgroup subsystem for use as general purpose socket classid marker that is
341 being used in cls_cgroup and for net 326 being used in cls_cgroup and for netfilter matching.
342 327
343 config NET_RX_BUSY_POLL 328 config NET_RX_BUSY_POLL
344 bool 329 bool
345 default y if !PREEMPT_RT || (PREEMPT_R 330 default y if !PREEMPT_RT || (PREEMPT_RT && !NETCONSOLE)
346 331
347 config BQL 332 config BQL
348 bool 333 bool
349 prompt "Enable Byte Queue Limits" <<
350 depends on SYSFS 334 depends on SYSFS
351 select DQL 335 select DQL
352 default y 336 default y
353 337
354 config BPF_STREAM_PARSER 338 config BPF_STREAM_PARSER
355 bool "enable BPF STREAM_PARSER" 339 bool "enable BPF STREAM_PARSER"
356 depends on INET 340 depends on INET
357 depends on BPF_SYSCALL 341 depends on BPF_SYSCALL
358 depends on CGROUP_BPF 342 depends on CGROUP_BPF
359 select STREAM_PARSER 343 select STREAM_PARSER
360 select NET_SOCK_MSG 344 select NET_SOCK_MSG
361 help 345 help
362 Enabling this allows a TCP stream pa 346 Enabling this allows a TCP stream parser to be used with
363 BPF_MAP_TYPE_SOCKMAP. 347 BPF_MAP_TYPE_SOCKMAP.
364 348
365 config NET_FLOW_LIMIT 349 config NET_FLOW_LIMIT
366 bool "Net flow limit" !! 350 bool
367 depends on RPS 351 depends on RPS
368 default y 352 default y
369 help 353 help
370 The network stack has to drop packet 354 The network stack has to drop packets when a receive processing CPU's
371 backlog reaches netdev_max_backlog. 355 backlog reaches netdev_max_backlog. If a few out of many active flows
372 generate the vast majority of load, 356 generate the vast majority of load, drop their traffic earlier to
373 maintain capacity for the other flow 357 maintain capacity for the other flows. This feature provides servers
374 with many clients some protection ag 358 with many clients some protection against DoS by a single (spoofed)
375 flow that greatly exceeds average wo 359 flow that greatly exceeds average workload.
376 360
377 menu "Network testing" 361 menu "Network testing"
378 362
379 config NET_PKTGEN 363 config NET_PKTGEN
380 tristate "Packet Generator (USE WITH C 364 tristate "Packet Generator (USE WITH CAUTION)"
381 depends on INET && PROC_FS 365 depends on INET && PROC_FS
382 help 366 help
383 This module will inject preconfigure 367 This module will inject preconfigured packets, at a configurable
384 rate, out of a given interface. It 368 rate, out of a given interface. It is used for network interface
385 stress testing and performance analy 369 stress testing and performance analysis. If you don't understand
386 what was just said, you don't need i 370 what was just said, you don't need it: say N.
387 371
388 Documentation on how to use the pack 372 Documentation on how to use the packet generator can be found
389 at <file:Documentation/networking/pk 373 at <file:Documentation/networking/pktgen.rst>.
390 374
391 To compile this code as a module, ch 375 To compile this code as a module, choose M here: the
392 module will be called pktgen. 376 module will be called pktgen.
393 377
394 config NET_DROP_MONITOR 378 config NET_DROP_MONITOR
395 tristate "Network packet drop alerting 379 tristate "Network packet drop alerting service"
396 depends on INET && TRACEPOINTS 380 depends on INET && TRACEPOINTS
397 help 381 help
398 This feature provides an alerting se 382 This feature provides an alerting service to userspace in the
399 event that packets are discarded in 383 event that packets are discarded in the network stack. Alerts
400 are broadcast via netlink socket to 384 are broadcast via netlink socket to any listening user space
401 process. If you don't need network 385 process. If you don't need network drop alerts, or if you are ok
402 just checking the various proc files 386 just checking the various proc files and other utilities for
403 drop statistics, say N here. 387 drop statistics, say N here.
404 388
405 endmenu 389 endmenu
406 390
407 endmenu 391 endmenu
408 392
409 source "net/ax25/Kconfig" 393 source "net/ax25/Kconfig"
410 source "net/can/Kconfig" 394 source "net/can/Kconfig"
411 source "net/bluetooth/Kconfig" 395 source "net/bluetooth/Kconfig"
412 source "net/rxrpc/Kconfig" 396 source "net/rxrpc/Kconfig"
413 source "net/kcm/Kconfig" 397 source "net/kcm/Kconfig"
414 source "net/strparser/Kconfig" 398 source "net/strparser/Kconfig"
415 source "net/mctp/Kconfig" 399 source "net/mctp/Kconfig"
416 400
417 config FIB_RULES 401 config FIB_RULES
418 bool 402 bool
419 403
420 menuconfig WIRELESS 404 menuconfig WIRELESS
421 bool "Wireless" 405 bool "Wireless"
422 depends on !S390 406 depends on !S390
423 default y 407 default y
424 408
425 if WIRELESS 409 if WIRELESS
426 410
427 source "net/wireless/Kconfig" 411 source "net/wireless/Kconfig"
428 source "net/mac80211/Kconfig" 412 source "net/mac80211/Kconfig"
429 413
430 endif # WIRELESS 414 endif # WIRELESS
431 415
432 source "net/rfkill/Kconfig" 416 source "net/rfkill/Kconfig"
433 source "net/9p/Kconfig" 417 source "net/9p/Kconfig"
434 source "net/caif/Kconfig" 418 source "net/caif/Kconfig"
435 source "net/ceph/Kconfig" 419 source "net/ceph/Kconfig"
436 source "net/nfc/Kconfig" 420 source "net/nfc/Kconfig"
437 source "net/psample/Kconfig" 421 source "net/psample/Kconfig"
438 source "net/ife/Kconfig" 422 source "net/ife/Kconfig"
439 423
440 config LWTUNNEL 424 config LWTUNNEL
441 bool "Network light weight tunnels" 425 bool "Network light weight tunnels"
442 help 426 help
443 This feature provides an infrastruct 427 This feature provides an infrastructure to support light weight
444 tunnels like mpls. There is no netde 428 tunnels like mpls. There is no netdevice associated with a light
445 weight tunnel endpoint. Tunnel encap 429 weight tunnel endpoint. Tunnel encapsulation parameters are stored
446 with light weight tunnel state assoc 430 with light weight tunnel state associated with fib routes.
447 431
448 config LWTUNNEL_BPF 432 config LWTUNNEL_BPF
449 bool "Execute BPF program as route nex 433 bool "Execute BPF program as route nexthop action"
450 depends on LWTUNNEL && INET 434 depends on LWTUNNEL && INET
451 default y if LWTUNNEL=y 435 default y if LWTUNNEL=y
452 help 436 help
453 Allows to run BPF programs as a next 437 Allows to run BPF programs as a nexthop action following a route
454 lookup for incoming and outgoing pac 438 lookup for incoming and outgoing packets.
455 439
456 config DST_CACHE 440 config DST_CACHE
457 bool 441 bool
458 default n 442 default n
459 443
460 config GRO_CELLS 444 config GRO_CELLS
461 bool 445 bool
462 default n 446 default n
463 447
464 config SOCK_VALIDATE_XMIT 448 config SOCK_VALIDATE_XMIT
465 bool 449 bool
466 450
467 config NET_IEEE8021Q_HELPERS <<
468 bool <<
469 <<
470 config NET_SELFTESTS 451 config NET_SELFTESTS
471 def_tristate PHYLIB 452 def_tristate PHYLIB
472 depends on PHYLIB && INET 453 depends on PHYLIB && INET
473 454
474 config NET_SOCK_MSG 455 config NET_SOCK_MSG
475 bool 456 bool
476 default n 457 default n
477 help 458 help
478 The NET_SOCK_MSG provides a framewor 459 The NET_SOCK_MSG provides a framework for plain sockets (e.g. TCP) or
479 ULPs (upper layer modules, e.g. TLS) 460 ULPs (upper layer modules, e.g. TLS) to process L7 application data
480 with the help of BPF programs. 461 with the help of BPF programs.
481 462
482 config NET_DEVLINK 463 config NET_DEVLINK
483 bool 464 bool
484 default n 465 default n
485 466
486 config PAGE_POOL 467 config PAGE_POOL
487 bool 468 bool
488 469
489 config PAGE_POOL_STATS 470 config PAGE_POOL_STATS
490 default n 471 default n
491 bool "Page pool stats" 472 bool "Page pool stats"
492 depends on PAGE_POOL 473 depends on PAGE_POOL
493 help 474 help
494 Enable page pool statistics to track 475 Enable page pool statistics to track page allocation and recycling
495 in page pools. This option incurs ad 476 in page pools. This option incurs additional CPU cost in allocation
496 and recycle paths and additional mem 477 and recycle paths and additional memory cost to store the statistics.
497 These statistics are only available 478 These statistics are only available if this option is enabled and if
498 the driver using the page pool suppo 479 the driver using the page pool supports exporting this data.
499 480
500 If unsure, say N. 481 If unsure, say N.
501 482
502 config FAILOVER 483 config FAILOVER
503 tristate "Generic failover module" 484 tristate "Generic failover module"
504 help 485 help
505 The failover module provides a gener 486 The failover module provides a generic interface for paravirtual
506 drivers to register a netdev and a s 487 drivers to register a netdev and a set of ops with a failover
507 instance. The ops are used as event 488 instance. The ops are used as event handlers that get called to
508 handle netdev register/unregister/li 489 handle netdev register/unregister/link change/name change events
509 on slave pci ethernet devices with t 490 on slave pci ethernet devices with the same mac address as the
510 failover netdev. This enables paravi 491 failover netdev. This enables paravirtual drivers to use a
511 VF as an accelerated low latency dat 492 VF as an accelerated low latency datapath. It also allows live
512 migration of VMs with direct attache 493 migration of VMs with direct attached VFs by failing over to the
513 paravirtual datapath when the VF is 494 paravirtual datapath when the VF is unplugged.
514 495
515 config ETHTOOL_NETLINK 496 config ETHTOOL_NETLINK
516 bool "Netlink interface for ethtool" 497 bool "Netlink interface for ethtool"
517 select DIMLIB <<
518 default y 498 default y
519 help 499 help
520 An alternative userspace interface f 500 An alternative userspace interface for ethtool based on generic
521 netlink. It provides better extensib 501 netlink. It provides better extensibility and some new features,
522 e.g. notification messages. 502 e.g. notification messages.
523 503
524 config NETDEV_ADDR_LIST_TEST 504 config NETDEV_ADDR_LIST_TEST
525 tristate "Unit tests for device addres 505 tristate "Unit tests for device address list"
526 default KUNIT_ALL_TESTS 506 default KUNIT_ALL_TESTS
527 depends on KUNIT 507 depends on KUNIT
528 508
529 config NET_TEST 509 config NET_TEST
530 tristate "KUnit tests for networking" 510 tristate "KUnit tests for networking" if !KUNIT_ALL_TESTS
531 depends on KUNIT 511 depends on KUNIT
532 default KUNIT_ALL_TESTS 512 default KUNIT_ALL_TESTS
533 help 513 help
534 KUnit tests covering core networking 514 KUnit tests covering core networking infra, such as sk_buff.
535 515
536 If unsure, say N. 516 If unsure, say N.
537 517
538 endif # if NET 518 endif # if NET
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.