-
Notifications
You must be signed in to change notification settings - Fork 13.5k
take into account the num of processes by ulimit #143614
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
@@ -440,13 +440,24 @@ pub fn available_parallelism() -> io::Result<NonZero<usize>> { | |||
} | |||
} | |||
} | |||
|
|||
let mut ulimit = u64::MAX; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The type is rlim_t
, this won't work on x86-32
#[cfg(any(target_os = "android", target_os = "linux"))] | ||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The above block has the same cfg
, this can be combined
Could you please put a more detailed description of how the problem is reproduced in the PR description? Or open a separate issue for it. The change here also needs comments, and the docs at https://doc.rust-lang.org/beta/std/thread/fn.available_parallelism.html should be updated if this winds up being accepted. Since this is a user-visible change this will need libs-api signoff, but first cc @cuviper since it looks like the issue shows up in Rayon (possibly rayon-rs/rayon#694?) |
The job Click to see the possible cause of the failure (guessed by this bot)
|
I doubt that this will be useful -- e.g. starting a number of threads equal to the current |
let mut r: libc::rlimit = unsafe { mem::zeroed() }; | ||
unsafe { | ||
if libc::getrlimit(libc::RLIMIT_NPROC, &mut r) == 0 { | ||
ulimit = r.rlim_max |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note, the "soft" rlim_cur
is the value that is currently enforced, while the "hard" rlim_max
is a limit on how high an unprivileged process can adjust its own rlim_cur
.
No description provided.