TileOS/tileos-system-adjustments
TileOS/tileos-system-adjustments
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix comments

Browse source
This commit is contained in:
Aleksey Samoilov 2024-03-07 11:28:23 +04:00
parent 55aaa1475d
commit b48540690c
Signed by: Sunderland93
GPG key ID: D3E730685C28F1FB
2 changed files with 12 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
debian/changelog vendored
View file

@ -1,3 +1,9 @@
tileos-system-adjustments (1.5.1~tileos) unstable; urgency=medium
* Fix comments
-- Aleksey Samoilov <samoilov.lex@gmail.com> Thu, 07 Mar 2024 11:27:49 +0400
tileos-system-adjustments (1.5~tileos) unstable; urgency=medium tileos-system-adjustments (1.5~tileos) unstable; urgency=medium
* Disable Kyber scheduler for SSD and set mq-deadline * Disable Kyber scheduler for SSD and set mq-deadline

12
etc/sysctl.d/tileos.conf
View file

@ -1,12 +1,12 @@
# Set the maximum watches on files # Set the maximum watches on files
fs.inotify.max_user_watches = 600000 fs.inotify.max_user_watches = 600000
For efficiency run-time is transferred between the global pool and CPU local # For efficiency run-time is transferred between the global pool and CPU local
"silos" in a batch fashion. This greatly reduces global accounting pressure # "silos" in a batch fashion. This greatly reduces global accounting pressure
on large systems. The amount transferred each time such an update is required # on large systems. The amount transferred each time such an update is required
is described as the "slice". # is described as the "slice".
Larger slice values will reduce transfer overheads, while smaller values allow # Larger slice values will reduce transfer overheads, while smaller values allow
for more fine-grained consumption. # for more fine-grained consumption.
kernel.sched_cfs_bandwidth_slice_us = 3000 kernel.sched_cfs_bandwidth_slice_us = 3000
# This file contains the maximum number of memory map areas a process may have. Memory map areas are used as a side-effect of calling malloc, directly by mmap, mprotect, and madvise, and also when loading shared libraries. # This file contains the maximum number of memory map areas a process may have. Memory map areas are used as a side-effect of calling malloc, directly by mmap, mprotect, and madvise, and also when loading shared libraries.