standard kernels that are not tweaked for lowlatency performance. This is only needed for so-called generic kernels, ie. Gunzip -c /proc/config.gz > config-$(uname -r) Do I really need a real-time kernel? If you can't find the config file for your kernel there is also the possibility to extract the config from /proc/config.gz if your kernel supports it ( CONFIG_IKCONFIG_PROC=y): Open it, and check if it has the following characteristics:ĬONFIG_HIGH_RES_TIMERS=y indicates your kernel has high resolution timer support, the CONFIG_NO_HZ_IDLE means your kernel is tickless and the CONFIG_PREEMPT options indicate you're either running a low-latency kernel ( CONFIG_PREEMPT) or a real-time kernel ( CONFIG_PREEMPT_RT_FULL). The configuration file with which this kernel was created can be found in /boot/config-5.17.1-rt17. Run uname -a to find out which kernel you're running: The procedure of recovering an unbootable system itself is beyond the scope of this Wiki but there are plenty of resources that explain this in detail. This way you can restore the original file in the case you made such a typo that the system has become unbootable. Before adding the noatime mount parameter you might want to make a backup of your existing and working fstab file: By implementing the modifications a step at a time it is easier to track down which modification is causing any unwanted behavior.Ī good habit is to always make backups of any files you're about to modify. This way you can verify if each modification does what it claims to do. It is also advised to try the modifications step by step, so do not implement them all at once. This doesn't guarantee though that these modifications work for all set-ups and these modifications shouldn't be used as is but should be adapted if possible to match your own set-up. The modifications discussed in the following sections have been tested thoroughly and a number of these modifications have been implemented in specialized distros like KXStudio and AVLinux.
0 kommentar(er)
