Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
Slurm
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
tud-zih-energy
Slurm
Commits
3d017a1b
Commit
3d017a1b
authored
11 years ago
by
Morris Jette
Browse files
Options
Downloads
Patches
Plain Diff
Expand core specialization documentation
Detail configuration requirements with respect to core/CPUs
parent
608f57d7
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/html/core_spec.shtml
+7
-2
7 additions, 2 deletions
doc/html/core_spec.shtml
with
7 additions
and
2 deletions
doc/html/core_spec.shtml
+
7
−
2
View file @
3d017a1b
...
@@ -57,8 +57,13 @@ job allocation request options, especially --cores-per-socket.</p>
...
@@ -57,8 +57,13 @@ job allocation request options, especially --cores-per-socket.</p>
<h2>System Configuration</h2>
<h2>System Configuration</h2>
<p>Core Specialization is only supported if <i>SelectType</i> is configured
<p>Core Specialization is only supported if <i>SelectType</i> is configured
as either <i>select/cons_res</i> or <i>select/cray</i>. A job's core
as either <i>select/cons_res</i> or <i>select/cray</i>. A job's core
specialization option will be silently cleared on other configurations.</p>
specialization option will be silently cleared on other configurations.
In addition, each compute node's core count must be configured or the CPUs
count must be configured to the node's core count.
If the core count is not configured and the CPUs value is configured to the
count of hyperthreads, then hyperthreads rather than cores will be reserved for
system use.</p>
<p style="text-align:center;">Last modified
8 November
201
3
</p>
<p style="text-align:center;">Last modified
7 February
201
4
</p>
<!--#include virtual="footer.txt"-->
<!--#include virtual="footer.txt"-->
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment