mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Norbert Lange <nolange79@gmail.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: musl@lists.openwall.com, Rich Felker <dalias@libc.org>
Subject: Re: [musl] [BUG] sysconf implementing _SC_NPROCESSORS_(CONF|ONLN) incorrectly
Date: Wed, 15 Apr 2020 11:57:16 +0200	[thread overview]
Message-ID: <CADYdroNF11=SCxyjJ2i7=cyjVTV0N6tNrYG8Ly2McrSDBsks6w@mail.gmail.com> (raw)
In-Reply-To: <87o8rtjcwj.fsf@mid.deneb.enyo.de>

[-- Attachment #1: Type: text/plain, Size: 1852 bytes --]

I can't comment on whether glibc should be emulated. The point I am trying
to make is that it might be better to let the compilation fail by default,
or not provide the function at all.

The implementation right now doesn't seem sufficient (to put it midly) and
it prevents detection and automatic fallbacks. For example trace-cmd would
do this, and would work nicely - but instead it will gets musls
implementation that's defeated by setting an affinity mask.

Florian Weimer <fw@deneb.enyo.de> schrieb am Mi., 15. Apr. 2020, 11:50:

> * Norbert Lange:
>
> > How should  one deal with this?
> > I understand that the semantics are vague, but given that musl now
> > implements this
> > function, it will make detection and fallback hard (especially as musl
> > doesn't wants to be identified by the likes of macros).
> >
> > As it is now, just using the affinity mask definitely cant be useful,
> > an application wanting that behavior should be patched to
> > use that function directly.
> > If musl would not define the _SC_NPROCESSORS_* macros (but still keep
> > the implementation),
> > this could be used for compile-time detection atleast. Enabling the
> > current implementation would be
> > just a matter of explicitly defining those macros.
>
> _SC_NPROCESSORS_* as implemented in glibc is bad because those values
> are not adjusted by cgroups, so it can grossly overestimate available
> resources.
>
> The cgroups interfaces themselves are not stable and very complicated.
> I don't think it's a good idea to target them, especially not from
> code that is expected to be linked statically into applications.
>
> Given that, I'm not sure that glibc's way is a significant
> improvement.  musl should perhaps be changed to cope more gracefully
> with a sched_getaffinity failure, though (by not reporting a UP
> environment by accident).
>

[-- Attachment #2: Type: text/html, Size: 2323 bytes --]

  reply	other threads:[~2020-04-15  9:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09 10:29 Norbert Lange
2020-04-09 18:18 ` Szabolcs Nagy
2020-04-09 18:31   ` Florian Weimer
2020-04-10  1:02     ` Rich Felker
2020-04-14 10:08       ` Florian Weimer
2020-04-14 15:55         ` Rich Felker
2020-04-14 16:55           ` Florian Weimer
2020-04-15  9:38             ` Norbert Lange
2020-04-15  9:50               ` Florian Weimer
2020-04-15  9:57                 ` Norbert Lange [this message]
2020-04-15 10:04                   ` Szabolcs Nagy
2020-04-15 16:01                     ` Rich Felker
2020-04-15 15:58                 ` Rich Felker

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='CADYdroNF11=SCxyjJ2i7=cyjVTV0N6tNrYG8Ly2McrSDBsks6w@mail.gmail.com' \
    --to=nolange79@gmail.com \
    --cc=dalias@libc.org \
    --cc=fw@deneb.enyo.de \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).