public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/28310] New: Do not use affinity mask for sysconf (_SC_NPROCESSORS_CONF)
Date: Mon, 06 Sep 2021 10:46:03 +0000 [thread overview]
Message-ID: <bug-28310-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28310
Bug ID: 28310
Summary: Do not use affinity mask for sysconf
(_SC_NPROCESSORS_CONF)
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: fweimer at redhat dot com
CC: drepper.fsp at gmail dot com
Target Milestone: ---
The change in bug 27645 breaks the top command in common hypervisor
configurations (and also other monitoring tools). That's far more drastic than
some container use case that does not even work reliably with most container
hosts (only those that lie about affinity masks or are very unusual in that
they do not oversubscribe CPUs).
Related commit:
commit 903bc7dcc2acafc40be11639767e10a2de712649
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date: Thu Mar 25 09:30:07 2021 -0300
linux: Use sched_getaffinity for __get_nprocs (BZ #27645)
Both the sysfs and procfs parsing (through GET_NPROCS_PARSER) are
removed in favor the syscall. The initial scratch buffer should
fit to most of the common usage (1024 bytes with maps to 8192 CPUs).
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-09-06 10:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 10:46 fweimer at redhat dot com [this message]
2021-09-06 13:28 ` [Bug libc/28310] " nsaenzju at redhat dot com
2021-09-06 18:04 ` adhemerval.zanella at linaro dot org
2021-09-27 12:33 ` adhemerval.zanella at linaro dot org
2023-11-03 12:37 ` rajis at linux dot ibm.com
2023-11-06 13:35 ` adhemerval.zanella at linaro dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-28310-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).