mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: __sched_cpucount returns garbage
Date: Sun, 30 Nov 2014 12:38:46 +0100	[thread overview]
Message-ID: <20141130113846.GC9258@port70.net> (raw)
In-Reply-To: <20141129233632.GA2146@newbook>

* Isaac Dunham <ibid.ag@gmail.com> [2014-11-29 15:36:33 -0800]:
> I noticed that nproc ended up on the toybox TODO list (via Tizen), and went
> poking about via strace and ltrace to see where it got the cpu count from.
> 
> In the process, I discovered that __sched_cpucount is returning garbage;

works here as expected:

#define _GNU_SOURCE
#include <sched.h>
int main()
{
	cpu_set_t s = {0};
	CPU_SET(3, &s);
	CPU_SET(7, &s);
	CPU_SET(24, &s);
	return __sched_cpucount(sizeof s, &s);
}

returns 3

> on Alpine Linux on my N270-based netbook (1 physical core but 
> hyperthreading makes it look like 2),
> nproc
> outputs a random number of CPUs ranging from 413 to 472.

see where the cpu_set_t argument comes from
(most likely sched_getaffinity syscall)
then see why that is broken

__sched_cpucount just counts bit flags

> ltrace indicates that this is calling __sched_cpucount() and printing 
> its return value.
> 
> nproc --all
> calls sysconf(_SC_NPROCESSORS_CONF) and gets the proper number of CPUs.
> 
> Thanks,
> Isaac Dunham


  reply	other threads:[~2014-11-30 11:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-29 23:36 Isaac Dunham
2014-11-30 11:38 ` Szabolcs Nagy [this message]
2014-12-03  0:11   ` Rich Felker
2014-12-03  1:33     ` Isaac Dunham
2014-12-03  2:48       ` Rich Felker
2014-12-03  3:19         ` 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=20141130113846.GC9258@port70.net \
    --to=nsz@port70.net \
    --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).