From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>,
"Dmitry V. Levin" <ldv@altlinux.org>
Subject: Re: [PATCH] linux: fix accuracy of get_nprocs and get_nprocs_conf [BZ #28865]
Date: Mon, 7 Feb 2022 09:07:44 -0300 [thread overview]
Message-ID: <9f8357d6-e64b-63d9-af5f-5a4fa8d0652d@linaro.org> (raw)
In-Reply-To: <871r0ec2cz.fsf@oldenburg.str.redhat.com>
On 07/02/2022 09:01, Florian Weimer wrote:
> * Adhemerval Zanella:
>
>>> But I think using sched_getaffinity as a fallback when /sys and /proc
>>> are not available makes somse. It's different form what we did
>>> temporarily (sched_getaffinity first).
>>
>> My concern is we start to see BZ#27645 again on environments that filter
>> out sysfs and provide a synthetic sched_getaffinity.
>
> Should we move the sched_getaffinity fallback after /proc, then?
Yeah, that was what I suggested in another reply.
next prev parent reply other threads:[~2022-02-07 12:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 21:24 Dmitry V. Levin
2022-02-07 11:25 ` Adhemerval Zanella
2022-02-07 11:44 ` Florian Weimer
2022-02-07 11:57 ` Adhemerval Zanella
2022-02-07 12:01 ` Florian Weimer
2022-02-07 12:07 ` Adhemerval Zanella [this message]
2022-02-07 11:51 ` Dmitry V. Levin
2022-02-07 12:01 ` Adhemerval Zanella
2022-02-07 13:45 ` Dmitry V. Levin
2022-02-07 13:57 ` [PATCH v2] " Dmitry V. Levin
2022-02-08 19:34 ` Adhemerval Zanella
2022-02-08 22:40 ` Dmitry V. Levin
2022-02-08 22:58 ` 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=9f8357d6-e64b-63d9-af5f-5a4fa8d0652d@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=ldv@altlinux.org \
--cc=libc-alpha@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).