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
21eed55d
Commit
21eed55d
authored
8 years ago
by
Brian Christiansen
Browse files
Options
Downloads
Patches
Plain Diff
Increase buffer to hold spool dir for cpufreq locks
parent
ab7ee2c6
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
src/common/cpu_frequency.c
+3
-2
3 additions, 2 deletions
src/common/cpu_frequency.c
with
3 additions
and
2 deletions
src/common/cpu_frequency.c
+
3
−
2
View file @
21eed55d
...
...
@@ -66,6 +66,7 @@
#define SYSFS_PATH_MAX 255
#define FREQ_LIST_MAX 32
#define GOV_NAME_LEN 24
#define SPOOL_LEN 128
#define GOV_CONSERVATIVE 0x01
#define GOV_ONDEMAND 0x02
...
...
@@ -127,7 +128,7 @@ static int _fd_lock_retry(int fd)
*/
static
int
_set_cpu_owner_lock
(
int
cpu_id
,
uint32_t
job_id
)
{
char
tmp
[
64
];
char
tmp
[
SPOOL_LEN
];
int
fd
,
sz
;
snprintf
(
tmp
,
sizeof
(
tmp
),
"%s/cpu"
,
slurmd_spooldir
);
...
...
@@ -152,7 +153,7 @@ static int _set_cpu_owner_lock(int cpu_id, uint32_t job_id)
static
int
_test_cpu_owner_lock
(
int
cpu_id
,
uint32_t
job_id
)
{
char
tmp
[
64
];
char
tmp
[
SPOOL_LEN
];
uint32_t
in_job_id
;
int
fd
,
sz
;
...
...
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