Skip to content

Commit f02cd4a

Browse files
committed
config-linux: mark memory.kernel[TCP] as NOT RECOMMENDED
Per-cgroup kernel memory accounting (and explicit limiting) is problematic in the Linux kernel for too many reasons to quote here. Besides, cgroup v2 does not even have a kernel memory limit knob, and the one in cgroup v1 is made obsoleted in kernel v5.4 [1]. Mark memory.kernel and memory.kernelTCP as NOT RECOMMENDED, in additon to OPTIONAL. This is a way to say "we do not anyone (runtimes or users) to set those limits, unless they have good understanding and strong reasons to do so". [1] torvalds/linux@0158115f702b0ba208ab0b Signed-off-by: Kir Kolyshkin <[email protected]>
1 parent 43e4633 commit f02cd4a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

config-linux.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -264,8 +264,8 @@ Values for memory specify the limit in bytes, or `-1` for unlimited memory.
264264
* **`limit`** *(int64, OPTIONAL)* - sets limit of memory usage
265265
* **`reservation`** *(int64, OPTIONAL)* - sets soft limit of memory usage
266266
* **`swap`** *(int64, OPTIONAL)* - sets limit of memory+Swap usage
267-
* **`kernel`** *(int64, OPTIONAL)* - sets hard limit for kernel memory
268-
* **`kernelTCP`** *(int64, OPTIONAL)* - sets hard limit for kernel TCP buffer memory
267+
* **`kernel`** *(int64, OPTIONAL, NOT RECOMMENDED)* - sets hard limit for kernel memory
268+
* **`kernelTCP`** *(int64, OPTIONAL, NOT RECOMMENDED)* - sets hard limit for kernel TCP buffer memory
269269

270270
The following properties do not specify memory limits, but are covered by the `memory` controller:
271271

0 commit comments

Comments
 (0)