Kernel Runtime Configuration: Difference between revisions
No edit summary |
|||
| Line 39: | Line 39: | ||
====net.core.netdev_max_backlog==== | ====net.core.netdev_max_backlog==== | ||
{{ | {{External2|https://access.redhat.com/solutions/1241943|https://wiki.mikejung.biz/Sysctl_tweaks#net.core.netdev_max_backlog}} | ||
'net.core.netdev_max_backlog' determines the maximum number of packets, queued on the INPUT side, when the interface receives packets faster than kernel can process them. | |||
==ipv4== | ==ipv4== | ||
Revision as of 18:21, 8 June 2017
External
- sysctl tweaks https://wiki.mikejung.biz/Sysctl_tweaks
Internal
fs
kernel
kernel.hostname
kernel.pid_max
Represents the maximum number of processes allowed on the system.
net
core
net.core.rmem_default
The default setting in bytes of the socket receive buffer. This may be set by the application using SO_RCVBUF socket option, up to net.core.rmem_max bytes. This value can be changed without reboot.
net.core.rmem_max
The maximum socket receive buffer size. Application can change the size of the receive buffer using SO_RCVBUF up to this limit. This value can be changed without reboot.
net.core.wmem_default
The default setting in bytes of the socket send buffer. This may be set by the application using SO_SNDBUF socket option, up to net.core.wmem_max bytes. This value can be changed without reboot.
net.core.wmem_max
The maximum socket receive buffer size. The socket buffer size may be set by using the SO_SNDBUF socket option. This value can be changed without reboot.
net.core.netdev_max_backlog
'net.core.netdev_max_backlog' determines the maximum number of packets, queued on the INPUT side, when the interface receives packets faster than kernel can process them.
ipv4
net.ipv4.tcp_rmem
10240 87380 12582912
net.ipv4.tcp_window_scaling
1