From ccff8454deabec8966d5356eb2db2b64290c1a66 Mon Sep 17 00:00:00 2001 From: Jiri Mencak Date: Fri, 29 Apr 2022 11:56:22 +0200 Subject: [PATCH] openshift profile: tuning for NVMe devices AWS Nitro instances need special tuning for NVMe devices: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html#timeout-nvme-ebs-volumes [sysfs] /sys/module/nvme_core/parameters/io_timeout=4294967295 /sys/module/nvme_core/parameters/max_retries=10 This tuning should probably be moved to Cloud Provider-specific profiles once the functionality is implemented. Signed-off-by: Jiri Mencak --- profiles/openshift/tuned.conf | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/profiles/openshift/tuned.conf b/profiles/openshift/tuned.conf index 9815fb9..ec4bf1a 100644 --- a/profiles/openshift/tuned.conf +++ b/profiles/openshift/tuned.conf @@ -25,6 +25,10 @@ net.ipv6.neigh.default.gc_thresh2=32768 net.ipv6.neigh.default.gc_thresh3=65536 vm.max_map_count=262144 +[sysfs] +/sys/module/nvme_core/parameters/io_timeout=4294967295 +/sys/module/nvme_core/parameters/max_retries=10 + [scheduler] # see rhbz#1979352; exclude containers from aligning to house keeping CPUs cgroup_ps_blacklist=/kubepods\.slice/