-
Notifications
You must be signed in to change notification settings - Fork 10
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
Expose more configuration options as environment variables #1380
Conversation
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferencesCodacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more |
2d80e98
to
1c610d9
Compare
…ons via environment variables
It's unused.
…ment variables into account as default
1c610d9
to
ee539c8
Compare
ee539c8
to
4a5b373
Compare
4a5b373
to
d932bdd
Compare
This exposes:
PIKA_IGNORE_PROCESS_MASK
PIKA_THREADS
PIKA_SCHEDULER
PIKA_BIND
as environment variables that can be used to set a default for the corresponding configuration options.
PIKA_SCHEDULER
corresponds topika.scheduler
and--pika:queueing
.--pika:queuing
has also been renamed to--pika:scheduler
here.Adds tests for the most important variables:
PIKA_THREADS
,PIKA_PROCESS_MASK
,PIKA_IGNORE_PROCESS_MASK
, andPIKA_BIND
.The following are also exposed in this PR as environment variables, but I don't intend to document them as I feel like they could be removed any time. They're exposed for development purposes only.
PIKA_AFFINITY
PIKA_PU_STEP
PIKA_PU_OFFSET
PIKA_NUMA_SENSITIVE