From: Robert Love <rml@tech9.net>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: Matthew Dobson <colpatch@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc-based cpu affinity user interface
Date: 10 Dec 2001 03:40:32 -0500 [thread overview]
Message-ID: <1007973633.874.38.camel@phantasy> (raw)
In-Reply-To: <200112100833.fBA8X6m209019@saturn.cs.uml.edu>
In-Reply-To: <200112100833.fBA8X6m209019@saturn.cs.uml.edu>
On Mon, 2001-12-10 at 03:33, Albert D. Cahalan wrote:
> It looks like you are limiting the number of CPUs to sizeof(long).
> Must you? Using "%lx" would be better in any case. Considering that
> you may outgrow the format, maybe this info doesn't belong in the
> /proc/*/stat files at all. For "ps" usage, a simple flag to indicate
> if the process is locked to a CPU would be OK. There are 3 cases
> of interest:
We already limit it... we use cpus_allowed and cpus_runnable which are
unsigned long.
Robert Love
next prev parent reply other threads:[~2001-12-10 8:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 20:23 [PATCH] proc-based cpu affinity user interface Matthew Dobson
2001-12-10 8:33 ` Albert D. Cahalan
2001-12-10 8:40 ` Robert Love [this message]
2001-12-10 9:37 ` Albert D. Cahalan
-- strict thread matches above, loose matches on Subject: below --
2001-11-27 3:31 Robert Love
2001-11-27 3:52 ` Davide Libenzi
2001-11-27 4:14 ` Robert Love
2001-11-27 4:39 ` Davide Libenzi
2001-11-27 4:48 ` Davide Libenzi
2001-11-27 14:17 ` Ingo Molnar
2001-11-27 16:49 ` Davide Libenzi
2001-11-27 18:46 ` Ingo Molnar
2001-11-27 4:37 ` Anton Blanchard
2001-11-27 5:08 ` Robert Love
2001-11-27 5:42 ` Tim Hockin
2001-11-27 6:25 ` Andreas Dilger
2001-11-27 6:40 ` Robert Love
2001-11-27 11:52 ` Ingo Molnar
2001-11-27 10:10 ` Alan Cox
2001-11-27 14:21 ` Ingo Molnar
2001-11-27 20:44 ` Robert Love
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=1007973633.874.38.camel@phantasy \
--to=rml@tech9.net \
--cc=acahalan@cs.uml.edu \
--cc=colpatch@us.ibm.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.