From 323cdb6a177db8c4c90d500ba16cfd2aea3e7025 Mon Sep 17 00:00:00 2001 From: Frank Sundermeyer Date: Tue, 5 Aug 2025 17:44:44 +0200 Subject: [PATCH] Adding a revision date to all chapters/parts --- xml/MAIN.SLERT.xml | 38 +++++++++++++------- xml/common_copyright_gfdl.xml | 15 ++++++-- xml/common_legal.xml | 16 ++++++--- xml/slert_cpuset_manipulation.xml | 60 +++++++++++++++++-------------- xml/slert_gettinghelp.xml | 16 ++++++--- xml/slert_intro.xml | 16 ++++++--- xml/slert_shielding_model.xml | 40 +++++++++++---------- xml/slert_usingshortcuts.xml | 22 ++++++++---- 8 files changed, 145 insertions(+), 78 deletions(-) diff --git a/xml/MAIN.SLERT.xml b/xml/MAIN.SLERT.xml index a8b6ebb..cbd9baf 100644 --- a/xml/MAIN.SLERT.xml +++ b/xml/MAIN.SLERT.xml @@ -1,19 +1,15 @@ - - - + %entities; ]> - - + + + &slert; Documentation - + &productname; &productnameshort; &productnumber; @@ -26,12 +22,30 @@ no + + + 2020-02-04 + + + + + Quick Start Manuals + + + + 2020-02-04 + + + + + + diff --git a/xml/common_copyright_gfdl.xml b/xml/common_copyright_gfdl.xml index d20663a..09e4a27 100644 --- a/xml/common_copyright_gfdl.xml +++ b/xml/common_copyright_gfdl.xml @@ -1,9 +1,9 @@ - - + %entities; ]> + + + + 2016-12-23 + + + + + + Copyright © 2006– SUSE LLC and contributors. All rights reserved. diff --git a/xml/common_legal.xml b/xml/common_legal.xml index 484580b..e6fb96e 100644 --- a/xml/common_legal.xml +++ b/xml/common_legal.xml @@ -1,13 +1,21 @@ - - + %entities; ]> + GNU Licenses - + + + 2015-12-15 + + + + + + This appendix contains the GNU Free Documentation License version 1.2. diff --git a/xml/slert_cpuset_manipulation.xml b/xml/slert_cpuset_manipulation.xml index c1a875a..afa8e54 100644 --- a/xml/slert_cpuset_manipulation.xml +++ b/xml/slert_cpuset_manipulation.xml @@ -1,13 +1,21 @@ - - + %entities; ]> + Full Featured Cpuset Manipulation Commands - + + + 2019-07-30 + + + + + + While basic shielding as described above is useful and a common use model for cset, there comes a time when more functionality @@ -31,7 +39,7 @@ The basic syntax of set for cpuset creation is: &prompt.user;cset set -c 1-3 -s my_cpuset1 -cset: --> created cpuset "my_cpuset1" +cset: --> created cpuset "my_cpuset1" This creates a cpuset named my_cpuset1 with a CPUSPEC of CPU1, CPU2 and CPU3. The CPUSPEC is the same concept as described in @@ -50,7 +58,7 @@ cset: --> created cpuset "my_cpuset1" omit CPU2), then issue the following command. &prompt.user;cset set -c 1,3 -s my_cpuset1 -cset: --> modified cpuset "my_cpuset +cset: --> modified cpuset "my_cpuset cset will then adjust the CPUs that are assigned to the my_cpuset1 set to only use CPU1 and CPU3. @@ -60,7 +68,7 @@ cset: --> modified cpuset "my_cpuset example: &prompt.user;cset set -s my_cpuset1 -n super_set -cset: --> renaming "/cpusets/my_cpuset1" to "super_set" +cset: --> renaming "/cpusets/my_cpuset1" to "super_set" Renames the cpuset called my_cpuset1 to super_set. @@ -70,8 +78,8 @@ cset: --> renaming "/cpusets/my_cpuset1" to "super_set" follows. &prompt.user;cset set -d super_set -cset: --> processing cpuset "super_set", moving 0 tasks to parent "/"... -cset: --> deleting cpuset "/super_set" +cset: --> processing cpuset "super_set", moving 0 tasks to parent "/"... +cset: --> deleting cpuset "/super_set" cset: done This command destroys the newly created cpuset called @@ -99,11 +107,11 @@ cset: done example: &prompt.user;cset set -c 1,3 -s top_set -cset: --> created cpuset "top_set" +cset: --> created cpuset "top_set" &prompt.user;cset set -c 3 -s /top_set/sub_set -cset: --> created cpuset "/top_set/sub_set" +cset: --> created cpuset "/top_set/sub_set" These commands created two cpusets: top_set and sub_set. The top_set uses CPU1 and @@ -114,7 +122,7 @@ cset: --> created cpuset "/top_set/sub_set" ask you to use the path. For example: &prompt.user;cset set -c 1,3 -s sub_set -cset: --> modified cpuset "sub_set +cset: --> modified cpuset "sub_set This command adds CPU1 to the sub_set cpuset for its use. Note that using the path in this case is optional. @@ -312,7 +320,7 @@ alext 16165 1 Soth beagled /usr/lib64/beagle/BeagleDaemon.exe --bg --auto cset: "two" cpuset of CPUSPEC(2) with 0 tasks running &prompt.user;cset proc -s two -e bash -cset: --> last message, executed args into cpuset "/two", new pid is: 20955 +cset: --> last message, executed args into cpuset "/two", new pid is: 20955 &prompt.user;cset proc -l -s two cset: "two" cpuset of CPUSPEC(2) with 2 tasks running @@ -372,8 +380,8 @@ root 21147 21118 Roth python ./cset proc -l two &prompt.user;cset proc -s two -e blah-blah -cset: --> last message, executed args into cpuset "/two", new pid is: 21655 -cset: **> [Errno 2] No such file or directory +cset: --> last message, executed args into cpuset "/two", new pid is: 21655 +cset: **> [Errno 2] No such file or directory The result is no new process even though a new PID is output. The reason for the message is of course that the cset process @@ -609,7 +617,7 @@ three 3 n 0 n 10 0 /three &prompt.user;cset proc -k -f root -t two cset: moving all kernel threads from / to /two cset: moving 70 kernel threads to: /two -cset: --> not moving 76 threads (not unbound, use --force) +cset: --> not moving 76 threads (not unbound, use --force) [==================================================]% cset: done @@ -627,7 +635,7 @@ cset: done &prompt.user;cset proc -k -f two -t root cset: moving all kernel threads from /two to / cset: ** no task matched move criteria -cset: **> kernel tasks are bound, use --force if ok +cset: **> kernel tasks are bound, use --force if ok &prompt.user;cset set -l -s two @@ -728,11 +736,11 @@ cset: done &prompt.user;cset set -c 0 -s system -cset: --> created cpuset "system" +cset: --> created cpuset "system" &prompt.user;cset set -c 1-3 -s user -cset: --> created cpuset "user" +cset: --> created cpuset "user" &prompt.user;cset set -l @@ -778,7 +786,7 @@ system 0 n 0 n 187 0 /system &prompt.user;cset proc -k -f root -t system cset: moving all kernel threads from / to /system cset: moving 70 kernel threads to: /system -cset: --> not moving 76 threads (not unbound, use --force) +cset: --> not moving 76 threads (not unbound, use --force) [==================================================]% cset: done @@ -881,23 +889,23 @@ root 0-3 y 0 y 344 0 / &prompt.user;cset set -c 0-3 prio_all -cset: --> created cpuset "prio_all" +cset: --> created cpuset "prio_all" &prompt.user;cset set -c 1-3 /prio_all/prio_high -cset: --> created cpuset "/prio_all/prio_high" +cset: --> created cpuset "/prio_all/prio_high" &prompt.user;cset set -c 2-3 /prio_all/prio_high/prio_med -cset: --> created cpuset "/prio_all/prio_high/prio_med" +cset: --> created cpuset "/prio_all/prio_high/prio_med" &prompt.user;cset set -c 3 /prio_all/prio_high/prio_med/prio_low -cset: --> created cpuset "/prio_all/prio_high/prio_med/prio_low" +cset: --> created cpuset "/prio_all/prio_high/prio_med/prio_low" &prompt.user;cset set -c 0 system -cset: --> created cpuset "system" +cset: --> created cpuset "system" &prompt.user;cset set -l -r @@ -931,7 +939,7 @@ prio_low 3 n 0 n 0 0 /prio_all/pr...rio_med/prio_low not moving 76 threads (not unbound, use --force) +cset: --> not moving 76 threads (not unbound, use --force) [==================================================]% cset: done diff --git a/xml/slert_gettinghelp.xml b/xml/slert_gettinghelp.xml index dab1deb..59f906b 100644 --- a/xml/slert_gettinghelp.xml +++ b/xml/slert_gettinghelp.xml @@ -1,13 +1,21 @@ - - + %entities; ]> + What to Do If There Are Problems - + + + 2019-08-08 + + + + + + If you encounter any issues with the cset application, you can file a bug report here: diff --git a/xml/slert_intro.xml b/xml/slert_intro.xml index 87bb9ed..e9f4b97 100644 --- a/xml/slert_intro.xml +++ b/xml/slert_intro.xml @@ -1,13 +1,21 @@ - - + %entities; ]> + Introduction - + + + 2019-07-30 + + + + + + In the Linux kernel, the cpuset facility provides a mechanism for creating logical entities called cpusets that encompass definitions diff --git a/xml/slert_shielding_model.xml b/xml/slert_shielding_model.xml index 13c82f2..4f56d3d 100644 --- a/xml/slert_shielding_model.xml +++ b/xml/slert_shielding_model.xml @@ -1,15 +1,20 @@ - - + %entities; ]> - + The Basic Shielding Model - + + + 2019-11-27 + + + + + + Although any setup of &cpuset;s can really be described as shielding, there is one prevalent shielding model in @@ -107,7 +112,7 @@ processing, issue the following command. &prompt.user;cset shield -c 1-3 -cset: --> activating shielding: +cset: --> activating shielding: cset: moving 176 tasks from root into system cpuset... [==================================================]% cset: "system" cpuset of CPUSPEC(0) with 176 tasks running @@ -138,7 +143,7 @@ cset: "user" cpuset of CPUSPEC(1-3) with 0 tasks running the current status of the shield again, issue this command: &prompt.user;cset shield -cset: --> shielding system active with +cset: --> shielding system active with cset: "system" cpuset of CPUSPEC(0) with 176 tasks running cset: "user" cpuset of CPUSPEC(1-3) with 0 tasks running @@ -179,21 +184,20 @@ cset: "user" cpuset of CPUSPEC(1-3) with 0 tasks running system set with the following command. &prompt.user;cset shield -k on -cset: --> activating kthread shielding +cset: --> activating kthread shielding cset: kthread shield activated, moving 70 tasks into system cpuset... [==================================================]% cset: done You can see that this moved an additional 70 tasks to the unshielded - system &cpuset;. Note that the / parameter can be given at the shield's + system &cpuset;. Note that the / parameter can be given at the shield's creation time. You do not need to perform these two steps separately if you know you will want kernel thread shielding as well. Executing cset shield again shows us the current state of the shield. &prompt.user;cset shield -cset: --> shielding system active with +cset: --> shielding system active with cset: "system" cpuset of CPUSPEC(0) with 246 tasks running cset: "user" cpuset of CPUSPEC(1-3) with 0 tasks running @@ -236,7 +240,7 @@ root 32653 25222 Roth python ./cset shield --unshield -v access to all resources on the system. For example: &prompt.user;cset shield --reset -cset: --> deactivating/reseting shielding +cset: --> deactivating/reseting shielding cset: moving 0 tasks from "/user" user set to root set... cset: moving 250 tasks from "/system" system set to root set... [==================================================]% @@ -279,7 +283,7 @@ cset: done &prompt.user;cset shield -e bash -cset: --> last message, executed args into cpuset "/user", new pid is: 13300 +cset: --> last message, executed args into cpuset "/user", new pid is: 13300 &prompt.user;cset shield -s -v @@ -348,7 +352,7 @@ cset: done and options for execution as follows. &prompt.user;cset shield --user=alext --group=users -e bash -cset: --> last message, executed args into cpuset "/user", new pid is: 14212 +cset: --> last message, executed args into cpuset "/user", new pid is: 14212 &prompt.user;cset shield -s -v @@ -437,7 +441,7 @@ alext 14241 14212 Roth python ./cset shield -s -v &prompt.user;cset shield -s -p 22010-22020 -cset: --> shielding following pidspec: 22010-22020 +cset: --> shielding following pidspec: 22010-22020 cset: done @@ -451,7 +455,7 @@ cset: done &prompt.user;cset shield -u -p $$ -cset: --> unshielding following pidspec: 22018 +cset: --> unshielding following pidspec: 22018 cset: done diff --git a/xml/slert_usingshortcuts.xml b/xml/slert_usingshortcuts.xml index a98443c..de0ebfa 100644 --- a/xml/slert_usingshortcuts.xml +++ b/xml/slert_usingshortcuts.xml @@ -1,13 +1,21 @@ - - + %entities; ]> + Using Shortcuts - + + + 2019-07-30 + + + + + + The commands listed in the previous sections always used all the required options. However, cset does have a shortcut facility @@ -253,12 +261,12 @@ cset se -d myset yourset ourset ---> destroys cpusets: myset, yourset and ourset +--> destroys cpusets: myset, yourset and ourset cset se -l prio_high prio_med prio_low ---> lists only cpusets prio_high, prio_med and prio_low ---> the -l is optional in this case since list is default +--> lists only cpusets prio_high, prio_med and prio_low +--> the -l is optional in this case since list is default <command>proc</command> Subcommand Shortcuts