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