tastytea
/
blog
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

cgroup: Clarify that cpu.weight.nice is not the same as nice.

This commit is contained in:
tastytea 2021-07-17 23:00:41 +02:00
parent acff616155
commit 0ed42ef450
Signed by: tastytea
GPG Key ID: CFC39497F1B26E07
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
content/posts/cgroup v2 by hand.adoc
View File

@ -99,9 +99,9 @@ Try adding your current shell to the group with `echo "$$" > cgroup.procs`. All
processes you start from this shell are now in the same cgroup. But what does processes you start from this shell are now in the same cgroup. But what does
the example do, exactly? the example do, exactly?
- *cpu.weight.nice* works like the link:{url-nice}[nice] command and has a range - *cpu.weight.nice* works like the link:{url-nice}[nice] command (but it is not
from -20 to 19. It is an alternate interface to *cpu.weight* which has a range the same) and has a range from -20 to 19. It is an alternate interface to
from 1 to 10,000. *cpu.weight* which has a range from 1 to 10,000.
- *cpu.max* sets the “maximum bandwidth limit”. We told the kernel that the - *cpu.max* sets the “maximum bandwidth limit”. We told the kernel that the
processes should use at most 200,000 µs every 100,000 µs, meaning they can use processes should use at most 200,000 µs every 100,000 µs, meaning they can use
the power of up to 2 cores. the power of up to 2 cores.