Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

Merge branch 'another-ip-sysctl-docs-cleanup'

Bagas Sanjaya says:

====================
Another ip-sysctl docs cleanup

Inspired by Abdelrahman's cleanup [1]. This time, mostly formatting
conversion to bullet lists.

[1]: https://lore.kernel.org/linux-doc/20250624150923.40590-1-abdelrahmanfekry375@gmail.com/
====================

Link: https://patch.msgid.link/20250701031300.19088-1-bagasdotme@gmail.com
Signed-off-by: Paolo Abeni <pabeni@redhat.com>

Paolo Abeni 12967695 792eacd3

+38 -38
+38 -38
Documentation/networking/ip-sysctl.rst
··· 1891 1891 1892 1892 This technology is known by different names: 1893 1893 1894 - In RFC 3069 it is called VLAN Aggregation. 1895 - Cisco and Allied Telesyn call it Private VLAN. 1896 - Hewlett-Packard call it Source-Port filtering or port-isolation. 1897 - Ericsson call it MAC-Forced Forwarding (RFC Draft). 1894 + - In RFC 3069 it is called VLAN Aggregation. 1895 + - Cisco and Allied Telesyn call it Private VLAN. 1896 + - Hewlett-Packard call it Source-Port filtering or port-isolation. 1897 + - Ericsson call it MAC-Forced Forwarding (RFC Draft). 1898 1898 1899 1899 proxy_delay - INTEGER 1900 1900 Delay proxy response. ··· 2487 2487 ioam6_id - INTEGER 2488 2488 Define the IOAM id of this node. Uses only 24 bits out of 32 in total. 2489 2489 2490 - Min: 0 2491 - Max: 0xFFFFFF 2490 + Possible value range: 2491 + 2492 + - Min: 0 2493 + - Max: 0xFFFFFF 2492 2494 2493 2495 Default: 0xFFFFFF 2494 2496 ··· 2498 2496 Define the wide IOAM id of this node. Uses only 56 bits out of 64 in 2499 2497 total. Can be different from ioam6_id. 2500 2498 2501 - Min: 0 2502 - Max: 0xFFFFFFFFFFFFFF 2499 + Possible value range: 2500 + 2501 + - Min: 0 2502 + - Max: 0xFFFFFFFFFFFFFF 2503 2503 2504 2504 Default: 0xFFFFFFFFFFFFFF 2505 2505 ··· 3326 3322 https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-failover for 3327 3323 details. 3328 3324 3329 - 1: Enable pf. 3325 + Possible values: 3330 3326 3331 - 0: Disable pf. 3327 + - 1: Enable pf. 3328 + - 0: Disable pf. 3332 3329 3333 3330 Default: 1 3334 3331 3335 3332 pf_expose - INTEGER 3336 3333 Unset or enable/disable pf (pf is short for potentially failed) state 3337 3334 exposure. Applications can control the exposure of the PF path state 3338 - in the SCTP_PEER_ADDR_CHANGE event and the SCTP_GET_PEER_ADDR_INFO 3339 - sockopt. When it's unset, no SCTP_PEER_ADDR_CHANGE event with 3340 - SCTP_ADDR_PF state will be sent and a SCTP_PF-state transport info 3341 - can be got via SCTP_GET_PEER_ADDR_INFO sockopt; When it's enabled, 3342 - a SCTP_PEER_ADDR_CHANGE event will be sent for a transport becoming 3343 - SCTP_PF state and a SCTP_PF-state transport info can be got via 3344 - SCTP_GET_PEER_ADDR_INFO sockopt; When it's disabled, no 3345 - SCTP_PEER_ADDR_CHANGE event will be sent and it returns -EACCES when 3346 - trying to get a SCTP_PF-state transport info via SCTP_GET_PEER_ADDR_INFO 3347 - sockopt. 3335 + in the SCTP_PEER_ADDR_CHANGE event and access of SCTP_PF-state 3336 + transport info via SCTP_GET_PEER_ADDR_INFO sockopt. 3348 3337 3349 - 0: Unset pf state exposure, Compatible with old applications. 3338 + Possible values: 3350 3339 3351 - 1: Disable pf state exposure. 3352 - 3353 - 2: Enable pf state exposure. 3340 + - 0: Unset pf state exposure (compatible with old applications). No 3341 + event will be sent but the transport info can be queried. 3342 + - 1: Disable pf state exposure. No event will be sent and trying to 3343 + obtain transport info will return -EACCESS. 3344 + - 2: Enable pf state exposure. The event will be sent for a transport 3345 + becoming SCTP_PF state and transport info can be obtained. 3354 3346 3355 3347 Default: 0 3356 3348 ··· 3542 3542 sctp_mem - vector of 3 INTEGERs: min, pressure, max 3543 3543 Number of pages allowed for queueing by all SCTP sockets. 3544 3544 3545 - min: Below this number of pages SCTP is not bothered about its 3546 - memory appetite. When amount of memory allocated by SCTP exceeds 3547 - this number, SCTP starts to moderate memory usage. 3548 - 3549 - pressure: This value was introduced to follow format of tcp_mem. 3550 - 3551 - max: Number of pages allowed for queueing by all SCTP sockets. 3545 + * min: Below this number of pages SCTP is not bothered about its 3546 + memory usage. When amount of memory allocated by SCTP exceeds 3547 + this number, SCTP starts to moderate memory usage. 3548 + * pressure: This value was introduced to follow format of tcp_mem. 3549 + * max: Maximum number of allowed pages. 3552 3550 3553 3551 Default is calculated at boot time from amount of available memory. 3554 3552 ··· 3554 3556 Only the first value ("min") is used, "default" and "max" are 3555 3557 ignored. 3556 3558 3557 - min: Minimal size of receive buffer used by SCTP socket. 3558 - It is guaranteed to each SCTP socket (but not association) even 3559 - under moderate memory pressure. 3559 + * min: Minimal size of receive buffer used by SCTP socket. 3560 + It is guaranteed to each SCTP socket (but not association) even 3561 + under moderate memory pressure. 3560 3562 3561 3563 Default: 4K 3562 3564 ··· 3564 3566 Only the first value ("min") is used, "default" and "max" are 3565 3567 ignored. 3566 3568 3567 - min: Minimum size of send buffer that can be used by SCTP sockets. 3568 - It is guaranteed to each SCTP socket (but not association) even 3569 - under moderate memory pressure. 3569 + * min: Minimum size of send buffer that can be used by SCTP sockets. 3570 + It is guaranteed to each SCTP socket (but not association) even 3571 + under moderate memory pressure. 3570 3572 3571 3573 Default: 4K 3572 3574 3573 3575 addr_scope_policy - INTEGER 3574 - Control IPv4 address scoping - draft-stewart-tsvwg-sctp-ipv4-00 3576 + Control IPv4 address scoping (see 3577 + https://datatracker.ietf.org/doc/draft-stewart-tsvwg-sctp-ipv4/00/ 3578 + for details). 3575 3579 3576 3580 - 0 - Disable IPv4 address scoping 3577 3581 - 1 - Enable IPv4 address scoping