]>
Commit | Line | Data |
---|---|---|
faa5273c | 1 | Documentation for /proc/sys/net/* |
760df93e SF |
2 | (c) 1999 Terrehon Bowden <terrehon@pacbell.net> |
3 | Bodo Bauer <bb@ricochet.net> | |
4 | (c) 2000 Jorge Nerin <comandante@zaralinux.com> | |
5 | (c) 2009 Shen Feng <shen@cn.fujitsu.com> | |
6 | ||
7 | For general info and legal blurb, please look in README. | |
8 | ||
9 | ============================================================== | |
10 | ||
11 | This file contains the documentation for the sysctl files in | |
faa5273c | 12 | /proc/sys/net |
760df93e SF |
13 | |
14 | The interface to the networking parts of the kernel is located in | |
faa5273c | 15 | /proc/sys/net. The following table shows all possible subdirectories. You may |
760df93e SF |
16 | see only some of them, depending on your kernel's configuration. |
17 | ||
18 | ||
19 | Table : Subdirectories in /proc/sys/net | |
20 | .............................................................................. | |
21 | Directory Content Directory Content | |
22 | core General parameter appletalk Appletalk protocol | |
23 | unix Unix domain sockets netrom NET/ROM | |
24 | 802 E802 protocol ax25 AX25 | |
25 | ethernet Ethernet protocol rose X.25 PLP layer | |
26 | ipv4 IP version 4 x25 X.25 protocol | |
27 | ipx IPX token-ring IBM token ring | |
28 | bridge Bridging decnet DEC net | |
cc79dd1b | 29 | ipv6 IP version 6 tipc TIPC |
760df93e SF |
30 | .............................................................................. |
31 | ||
32 | 1. /proc/sys/net/core - Network core options | |
33 | ------------------------------------------------------- | |
34 | ||
0a14842f ED |
35 | bpf_jit_enable |
36 | -------------- | |
37 | ||
38 | This enables Berkeley Packet Filter Just in Time compiler. | |
014cd0a3 ME |
39 | |
40 | There are two flavors of JIT, the new eBPF JIT supported on: | |
41 | - x86_64 | |
42 | - arm64 | |
43 | - ppc64 | |
44 | - sparc64 | |
45 | - mips64 | |
46 | ||
47 | And the older cBPF JIT supported on: | |
48 | - arm | |
49 | - mips | |
50 | - ppc | |
51 | - sparc | |
52 | ||
53 | The BPF JIT provides a framework to speed packet filtering, the one used by | |
54 | tcpdump/libpcap for example. | |
55 | ||
0a14842f ED |
56 | Values : |
57 | 0 - disable the JIT (default value) | |
58 | 1 - enable the JIT | |
59 | 2 - enable the JIT and ask the compiler to emit traces on kernel log. | |
60 | ||
4f3446bb DB |
61 | bpf_jit_harden |
62 | -------------- | |
63 | ||
64 | This enables hardening for the Berkeley Packet Filter Just in Time compiler. | |
65 | Supported are eBPF JIT backends. Enabling hardening trades off performance, | |
66 | but can mitigate JIT spraying. | |
67 | Values : | |
68 | 0 - disable JIT hardening (default value) | |
69 | 1 - enable JIT hardening for unprivileged users only | |
70 | 2 - enable JIT hardening for all users | |
71 | ||
74451e66 DB |
72 | bpf_jit_kallsyms |
73 | ---------------- | |
74 | ||
75 | When Berkeley Packet Filter Just in Time compiler is enabled, then compiled | |
76 | images are unknown addresses to the kernel, meaning they neither show up in | |
77 | traces nor in /proc/kallsyms. This enables export of these addresses, which | |
78 | can be used for debugging/tracing. If bpf_jit_harden is enabled, this feature | |
79 | is disabled. | |
80 | Values : | |
81 | 0 - disable JIT kallsyms export (default value) | |
82 | 1 - enable JIT kallsyms export for privileged users only | |
83 | ||
c60f6aa8 SW |
84 | dev_weight |
85 | -------------- | |
86 | ||
87 | The maximum number of packets that kernel can handle on a NAPI interrupt, | |
88 | it's a Per-CPU variable. | |
89 | Default: 64 | |
90 | ||
3d48b53f MT |
91 | dev_weight_rx_bias |
92 | -------------- | |
93 | ||
94 | RPS (e.g. RFS, aRFS) processing is competing with the registered NAPI poll function | |
95 | of the driver for the per softirq cycle netdev_budget. This parameter influences | |
96 | the proportion of the configured netdev_budget that is spent on RPS based packet | |
97 | processing during RX softirq cycles. It is further meant for making current | |
98 | dev_weight adaptable for asymmetric CPU needs on RX/TX side of the network stack. | |
99 | (see dev_weight_tx_bias) It is effective on a per CPU basis. Determination is based | |
100 | on dev_weight and is calculated multiplicative (dev_weight * dev_weight_rx_bias). | |
101 | Default: 1 | |
102 | ||
103 | dev_weight_tx_bias | |
104 | -------------- | |
105 | ||
106 | Scales the maximum number of packets that can be processed during a TX softirq cycle. | |
107 | Effective on a per CPU basis. Allows scaling of current dev_weight for asymmetric | |
108 | net stack processing needs. Be careful to avoid making TX softirq processing a CPU hog. | |
109 | Calculation is based on dev_weight (dev_weight * dev_weight_tx_bias). | |
110 | Default: 1 | |
111 | ||
6da7c8fc | 112 | default_qdisc |
113 | -------------- | |
114 | ||
115 | The default queuing discipline to use for network devices. This allows | |
2e64126b PS |
116 | overriding the default of pfifo_fast with an alternative. Since the default |
117 | queuing discipline is created without additional parameters so is best suited | |
118 | to queuing disciplines that work well without configuration like stochastic | |
119 | fair queue (sfq), CoDel (codel) or fair queue CoDel (fq_codel). Don't use | |
120 | queuing disciplines like Hierarchical Token Bucket or Deficit Round Robin | |
121 | which require setting up classes and bandwidths. Note that physical multiqueue | |
122 | interfaces still use mq as root qdisc, which in turn uses this default for its | |
123 | leaves. Virtual devices (like e.g. lo or veth) ignore this setting and instead | |
124 | default to noqueue. | |
6da7c8fc | 125 | Default: pfifo_fast |
126 | ||
64b0dc51 | 127 | busy_read |
06021292 | 128 | ---------------- |
e0d1095a | 129 | Low latency busy poll timeout for socket reads. (needs CONFIG_NET_RX_BUSY_POLL) |
cbf55001 | 130 | Approximate time in us to busy loop waiting for packets on the device queue. |
64b0dc51 ET |
131 | This sets the default value of the SO_BUSY_POLL socket option. |
132 | Can be set or overridden per socket by setting socket option SO_BUSY_POLL, | |
133 | which is the preferred method of enabling. If you need to enable the feature | |
134 | globally via sysctl, a value of 50 is recommended. | |
cbf55001 | 135 | Will increase power usage. |
06021292 ET |
136 | Default: 0 (off) |
137 | ||
64b0dc51 | 138 | busy_poll |
2d48d67f | 139 | ---------------- |
e0d1095a | 140 | Low latency busy poll timeout for poll and select. (needs CONFIG_NET_RX_BUSY_POLL) |
cbf55001 | 141 | Approximate time in us to busy loop waiting for events. |
2d48d67f ET |
142 | Recommended value depends on the number of sockets you poll on. |
143 | For several sockets 50, for several hundreds 100. | |
144 | For more than that you probably want to use epoll. | |
64b0dc51 ET |
145 | Note that only sockets with SO_BUSY_POLL set will be busy polled, |
146 | so you want to either selectively set SO_BUSY_POLL on those sockets or set | |
147 | sysctl.net.busy_read globally. | |
cbf55001 | 148 | Will increase power usage. |
2d48d67f ET |
149 | Default: 0 (off) |
150 | ||
760df93e SF |
151 | rmem_default |
152 | ------------ | |
153 | ||
154 | The default setting of the socket receive buffer in bytes. | |
155 | ||
156 | rmem_max | |
157 | -------- | |
158 | ||
159 | The maximum receive socket buffer size in bytes. | |
160 | ||
b245be1f WB |
161 | tstamp_allow_data |
162 | ----------------- | |
163 | Allow processes to receive tx timestamps looped together with the original | |
164 | packet contents. If disabled, transmit timestamp requests from unprivileged | |
165 | processes are dropped unless socket option SOF_TIMESTAMPING_OPT_TSONLY is set. | |
166 | Default: 1 (on) | |
167 | ||
168 | ||
760df93e SF |
169 | wmem_default |
170 | ------------ | |
171 | ||
172 | The default setting (in bytes) of the socket send buffer. | |
173 | ||
174 | wmem_max | |
175 | -------- | |
176 | ||
177 | The maximum send socket buffer size in bytes. | |
178 | ||
179 | message_burst and message_cost | |
180 | ------------------------------ | |
181 | ||
182 | These parameters are used to limit the warning messages written to the kernel | |
183 | log from the networking code. They enforce a rate limit to make a | |
184 | denial-of-service attack impossible. A higher message_cost factor, results in | |
185 | fewer messages that will be written. Message_burst controls when messages will | |
186 | be dropped. The default settings limit warning messages to one every five | |
187 | seconds. | |
188 | ||
189 | warnings | |
190 | -------- | |
191 | ||
ba7a46f1 JP |
192 | This sysctl is now unused. |
193 | ||
194 | This was used to control console messages from the networking stack that | |
195 | occur because of problems on the network like duplicate address or bad | |
196 | checksums. | |
197 | ||
198 | These messages are now emitted at KERN_DEBUG and can generally be enabled | |
199 | and controlled by the dynamic_debug facility. | |
760df93e SF |
200 | |
201 | netdev_budget | |
202 | ------------- | |
203 | ||
204 | Maximum number of packets taken from all interfaces in one polling cycle (NAPI | |
205 | poll). In one polling cycle interfaces which are registered to polling are | |
7acf8a1e MW |
206 | probed in a round-robin manner. Also, a polling cycle may not exceed |
207 | netdev_budget_usecs microseconds, even if netdev_budget has not been | |
208 | exhausted. | |
209 | ||
210 | netdev_budget_usecs | |
211 | --------------------- | |
212 | ||
213 | Maximum number of microseconds in one NAPI polling cycle. Polling | |
214 | will exit when either netdev_budget_usecs have elapsed during the | |
215 | poll cycle or the number of packets processed reaches netdev_budget. | |
760df93e SF |
216 | |
217 | netdev_max_backlog | |
218 | ------------------ | |
219 | ||
220 | Maximum number of packets, queued on the INPUT side, when the interface | |
221 | receives packets faster than kernel can process them. | |
222 | ||
960fb622 ED |
223 | netdev_rss_key |
224 | -------------- | |
225 | ||
226 | RSS (Receive Side Scaling) enabled drivers use a 40 bytes host key that is | |
227 | randomly generated. | |
228 | Some user space might need to gather its content even if drivers do not | |
229 | provide ethtool -x support yet. | |
230 | ||
231 | myhost:~# cat /proc/sys/net/core/netdev_rss_key | |
232 | 84:50:f4:00:a8:15:d1:a7:e9:7f:1d:60:35:c7:47:25:42:97:74:ca:56:bb:b6:a1:d8: ... (52 bytes total) | |
233 | ||
234 | File contains nul bytes if no driver ever called netdev_rss_key_fill() function. | |
235 | Note: | |
236 | /proc/sys/net/core/netdev_rss_key contains 52 bytes of key, | |
237 | but most drivers only use 40 bytes of it. | |
238 | ||
239 | myhost:~# ethtool -x eth0 | |
240 | RX flow hash indirection table for eth0 with 8 RX ring(s): | |
241 | 0: 0 1 2 3 4 5 6 7 | |
242 | RSS hash key: | |
243 | 84:50:f4:00:a8:15:d1:a7:e9:7f:1d:60:35:c7:47:25:42:97:74:ca:56:bb:b6:a1:d8:43:e3:c9:0c:fd:17:55:c2:3a:4d:69:ed:f1:42:89 | |
244 | ||
3b098e2d ED |
245 | netdev_tstamp_prequeue |
246 | ---------------------- | |
247 | ||
248 | If set to 0, RX packet timestamps can be sampled after RPS processing, when | |
249 | the target CPU processes packets. It might give some delay on timestamps, but | |
250 | permit to distribute the load on several cpus. | |
251 | ||
252 | If set to 1 (default), timestamps are sampled as soon as possible, before | |
253 | queueing. | |
254 | ||
760df93e SF |
255 | optmem_max |
256 | ---------- | |
257 | ||
258 | Maximum ancillary buffer size allowed per socket. Ancillary data is a sequence | |
259 | of struct cmsghdr structures with appended data. | |
260 | ||
261 | 2. /proc/sys/net/unix - Parameters for Unix domain sockets | |
262 | ------------------------------------------------------- | |
263 | ||
45dad7bd LX |
264 | There is only one file in this directory. |
265 | unix_dgram_qlen limits the max number of datagrams queued in Unix domain | |
ca8b9950 | 266 | socket's buffer. It will not take effect unless PF_UNIX flag is specified. |
760df93e SF |
267 | |
268 | ||
269 | 3. /proc/sys/net/ipv4 - IPV4 settings | |
270 | ------------------------------------------------------- | |
271 | Please see: Documentation/networking/ip-sysctl.txt and ipvs-sysctl.txt for | |
272 | descriptions of these entries. | |
273 | ||
274 | ||
275 | 4. Appletalk | |
276 | ------------------------------------------------------- | |
277 | ||
278 | The /proc/sys/net/appletalk directory holds the Appletalk configuration data | |
279 | when Appletalk is loaded. The configurable parameters are: | |
280 | ||
281 | aarp-expiry-time | |
282 | ---------------- | |
283 | ||
284 | The amount of time we keep an ARP entry before expiring it. Used to age out | |
285 | old hosts. | |
286 | ||
287 | aarp-resolve-time | |
288 | ----------------- | |
289 | ||
290 | The amount of time we will spend trying to resolve an Appletalk address. | |
291 | ||
292 | aarp-retransmit-limit | |
293 | --------------------- | |
294 | ||
295 | The number of times we will retransmit a query before giving up. | |
296 | ||
297 | aarp-tick-time | |
298 | -------------- | |
299 | ||
300 | Controls the rate at which expires are checked. | |
301 | ||
302 | The directory /proc/net/appletalk holds the list of active Appletalk sockets | |
303 | on a machine. | |
304 | ||
305 | The fields indicate the DDP type, the local address (in network:node format) | |
306 | the remote address, the size of the transmit pending queue, the size of the | |
307 | received queue (bytes waiting for applications to read) the state and the uid | |
308 | owning the socket. | |
309 | ||
310 | /proc/net/atalk_iface lists all the interfaces configured for appletalk.It | |
311 | shows the name of the interface, its Appletalk address, the network range on | |
312 | that address (or network number for phase 1 networks), and the status of the | |
313 | interface. | |
314 | ||
315 | /proc/net/atalk_route lists each known network route. It lists the target | |
316 | (network) that the route leads to, the router (may be directly connected), the | |
317 | route flags, and the device the route is using. | |
318 | ||
319 | ||
320 | 5. IPX | |
321 | ------------------------------------------------------- | |
322 | ||
323 | The IPX protocol has no tunable values in proc/sys/net. | |
324 | ||
325 | The IPX protocol does, however, provide proc/net/ipx. This lists each IPX | |
326 | socket giving the local and remote addresses in Novell format (that is | |
327 | network:node:port). In accordance with the strange Novell tradition, | |
328 | everything but the port is in hex. Not_Connected is displayed for sockets that | |
329 | are not tied to a specific remote address. The Tx and Rx queue sizes indicate | |
330 | the number of bytes pending for transmission and reception. The state | |
331 | indicates the state the socket is in and the uid is the owning uid of the | |
332 | socket. | |
333 | ||
334 | The /proc/net/ipx_interface file lists all IPX interfaces. For each interface | |
335 | it gives the network number, the node number, and indicates if the network is | |
336 | the primary network. It also indicates which device it is bound to (or | |
337 | Internal for internal networks) and the Frame Type if appropriate. Linux | |
338 | supports 802.3, 802.2, 802.2 SNAP and DIX (Blue Book) ethernet framing for | |
339 | IPX. | |
340 | ||
341 | The /proc/net/ipx_route table holds a list of IPX routes. For each route it | |
342 | gives the destination network, the router node (or Directly) and the network | |
343 | address of the router (or Connected) for internal networks. | |
cc79dd1b YX |
344 | |
345 | 6. TIPC | |
346 | ------------------------------------------------------- | |
347 | ||
a5325ae5 EH |
348 | tipc_rmem |
349 | ---------- | |
350 | ||
cc79dd1b YX |
351 | The TIPC protocol now has a tunable for the receive memory, similar to the |
352 | tcp_rmem - i.e. a vector of 3 INTEGERs: (min, default, max) | |
353 | ||
354 | # cat /proc/sys/net/tipc/tipc_rmem | |
355 | 4252725 34021800 68043600 | |
356 | # | |
357 | ||
358 | The max value is set to CONN_OVERLOAD_LIMIT, and the default and min values | |
359 | are scaled (shifted) versions of that same value. Note that the min value | |
360 | is not at this point in time used in any meaningful way, but the triplet is | |
361 | preserved in order to be consistent with things like tcp_rmem. | |
a5325ae5 EH |
362 | |
363 | named_timeout | |
364 | -------------- | |
365 | ||
366 | TIPC name table updates are distributed asynchronously in a cluster, without | |
367 | any form of transaction handling. This means that different race scenarios are | |
368 | possible. One such is that a name withdrawal sent out by one node and received | |
369 | by another node may arrive after a second, overlapping name publication already | |
370 | has been accepted from a third node, although the conflicting updates | |
371 | originally may have been issued in the correct sequential order. | |
372 | If named_timeout is nonzero, failed topology updates will be placed on a defer | |
373 | queue until another event arrives that clears the error, or until the timeout | |
374 | expires. Value is in milliseconds. |