From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Cc: Nicolas Saenz Julienne <nsaenzju@redhat.com>,
Florian Weimer <fweimer@redhat.com>
Subject: [PATCH 0/3] Revert the use of sched_getaffinity on get_nproc
Date: Mon, 6 Sep 2021 15:11:30 -0300 [thread overview]
Message-ID: <20210906181133.1401140-1-adhemerval.zanella@linaro.org> (raw)
The use of sched_getaffinity on get_nproc and
sysconf (_SC_NPROCESSORS_ONLN) done in 903bc7dcc2acafc40 (BZ #27645)
breaks the top command in common hypervisor configurations and also
other monitoring tools.
This patchset revert to previous strategy to obtain the system-wide
information first from sysfs, and then on procfs as a fallback.
The sched_getaffinity is still used on malloc code since it makes more
sense to get the per-process value to tune the maximum arena value.
Adhemerval Zanella (3):
misc: Add __get_nprocs_sched
linux: Simplify get_nprocs
linux: Revert the use of sched_getaffinity on get_nproc (BZ #28310)
include/sys/sysinfo.h | 7 +-
malloc/arena.c | 2 +-
misc/getsysstats.c | 6 +
posix/Makefile | 3 +-
sysdeps/mach/getsysstats.c | 6 +
sysdeps/unix/sysv/linux/getsysstats.c | 192 ++++++++++++++++++++------
6 files changed, 167 insertions(+), 49 deletions(-)
--
2.30.2
next reply other threads:[~2021-09-06 18:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 18:11 Adhemerval Zanella [this message]
2021-09-06 18:11 ` [PATCH 1/3] misc: Add __get_nprocs_sched Adhemerval Zanella
2021-09-06 18:11 ` [PATCH 2/3] linux: Simplify get_nprocs Adhemerval Zanella
2021-09-07 9:30 ` Florian Weimer
2021-09-07 12:05 ` Adhemerval Zanella
2021-09-07 9:44 ` Florian Weimer
2021-09-06 18:11 ` [PATCH 3/3] linux: Revert the use of sched_getaffinity on get_nproc (BZ #28310) Adhemerval Zanella
2021-09-07 9:45 ` Florian Weimer
2021-09-07 12:12 ` Adhemerval Zanella
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=20210906181133.1401140-1-adhemerval.zanella@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=nsaenzju@redhat.com \
/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).