Skip to content

Commit

Permalink
Described affinity inheritance in a little more detail
Browse files Browse the repository at this point in the history
  • Loading branch information
SystemXFiles committed Sep 27, 2024
1 parent 4ca5b76 commit 31cc438
Showing 1 changed file with 5 additions and 3 deletions.
8 changes: 5 additions & 3 deletions docs/rule_behavior_and_tips.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,8 +33,9 @@ first matching process rule.
## Core Affinity Inheritance in Windows

In **Windows**, child processes inherit the core affinity settings from their parent processes. For example, if the
parent process (`explorer.exe`) is restricted to cores 0 and 1, any process launched by it, such as `example.exe`, will
inherit this restriction and be limited to those same cores.
parent process (`explorer.exe`) is restricted to cores 0 and 1, any process launched by it, **for example,** `app.exe`,
will inherit this restriction and be limited to those same cores, unless the application itself or the user changes the
core affinity (for example, via Task Manager or Process Governor).

This behavior means you should carefully configure rules, especially when using wildcard rules like `*`, which apply to
[all processes](#rule-for-all-processes).
Expand Down Expand Up @@ -65,7 +66,8 @@ To apply a rule to all processes:

1. Go to the **Process Rules** tab.
2. Add a new rule.
3. Set **Process Selector** to `*` to match all processes (the `*` symbol acts as a wildcard, matching any sequence of characters in the process name).
3. Set **Process Selector** to `*` to match all processes (the `*` symbol acts as a wildcard, matching any sequence of
characters in the process name).
4. Configure the desired settings (e.g., affinity, priority).
5. Place this rule at the bottom of the list to allow more specific rules to take precedence.

Expand Down

0 comments on commit 31cc438

Please sign in to comment.