public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Andreas Jaeger <aj@suse.de>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: get_nprocs question
Date: Tue, 16 Mar 2004 20:12:00 -0000	[thread overview]
Message-ID: <40575FA6.50709@redhat.com> (raw)
In-Reply-To: <m3d67ch817.fsf@gromit.moeb>

Andreas Jaeger wrote:

> Here's the proposed patch.  Is this ok?

No.  The value returned never had a thread-specific value but with
getaffinity it would have.  The definition should stay as it it, the
affinity issue reducing the possible number of processors the
process/thread can run on is a different issue which needs a different
set of interfaces.

-- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖

  reply	other threads:[~2004-03-16 20:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-16  6:23 Andreas Jaeger
2004-03-16 20:05 ` Andreas Jaeger
2004-03-16 20:12   ` Ulrich Drepper [this message]
2004-03-17  5:33     ` Andreas Jaeger
2004-03-17  5:50       ` Ulrich Drepper

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=40575FA6.50709@redhat.com \
    --to=drepper@redhat.com \
    --cc=aj@suse.de \
    --cc=libc-hacker@sources.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).