You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Two changes:
* `nvme_core.io_timeout` is AWS-specific, move into AWS platform code
* `init_on_alloc` is enabled by default in the kernel config, so a
kernel arg is no-op and confusing (as removing it won't disable it)
Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
// init_on_alloc and init_on_free are not enforced, as they default to '1' in kernel config
21
-
// this way they can be overridden via installer extra args in case of severe performance issues
20
+
// init_on_alloc and init_on_free are not enforced, as:
21
+
// - init_on_alloc is enabled by default in the kernel config, but can be disabled with init_on_alloc=0 for performance reasons;
22
+
// - init_on_free is disabled by default in the kernel config, as it has a significant performance impact, and is not required for security when init_on_alloc=1 is enabled.
0 commit comments