Since commit 1033990ac5b2 ("sctp: implement memory accounting on tx path"), SCTP has supported memory accounting on tx path where 'sctp_wmem' is used by sk_wmem_schedule(). So we should fix the description for this option in ip-sysctl.rst accordingly. v1->v2: - Improve the description as Marcelo suggested.
Unified · Split
| @@ -2866,7 +2866,14 @@ sctp_rmem - vector of 3 INTEGERs: min, default, max · 2865 unmodified lines | |||
| 2866 | Default: 4K | 2866 | Default: 4K |
| 2867 | 2867 | ||
| 2868 | sctp_wmem - vector of 3 INTEGERs: min, default, max | 2868 | sctp_wmem - vector of 3 INTEGERs: min, default, max |
| 2869 | Currently this tunable has no effect. | 2869 | Only the first value ("min") is used, "default" and "max" are |
| 2870 | ignored. | ||
| 2871 | |||
| 2872 | min: Minimum size of send buffer that can be used by SCTP sockets. | ||
| 2873 | It is guaranteed to each SCTP socket (but not association) even | ||
| 2874 | under moderate memory pressure. | ||
| 2875 | |||
| 2876 | Default: 4K | ||
| 2870 | 2877 | ||
| 2871 | addr_scope_policy - INTEGER | 2878 | addr_scope_policy - INTEGER |
| 2872 | Control IPv4 address scoping - draft-stewart-tsvwg-sctp-ipv4-00 | 2879 | Control IPv4 address scoping - draft-stewart-tsvwg-sctp-ipv4-00 |