From: Robert Love <rml@tech9.net>
To: Anton Blanchard <anton@samba.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc-based cpu affinity user interface
Date: 27 Nov 2001 00:08:28 -0500 [thread overview]
Message-ID: <1006837709.971.6.camel@phantasy> (raw)
In-Reply-To: <20011127153740.A13824@krispykreme>
In-Reply-To: <1006831902.842.0.camel@phantasy> <20011127153740.A13824@krispykreme>
On Mon, 2001-11-26 at 23:37, Anton Blanchard wrote:
> > Attached is my procfs-based implementation of a user interface for
> > getting and setting a task's CPU affinity. Patch is against 2.4.16.
>
> Have you seen Andrew Mortons cpus_allowed patch?
No, although Andrew mentioned he had worked on it to me.
Looking it over...its of course very similar. One thing to note is his
patch doesn't incorporate the bits from Ingo's patch that I borrowed.
I.e., use of cpu_online_map, the forcing of the reschedule, etc. I
favor some of the differences in my variant.
I am glad to see he wrote a proc_write function, because I was worried I
was reimplementing something there, but I suppose not.
Either way, I'd like to see one of these in the kernel.
Robert Love
next prev parent reply other threads:[~2001-11-27 5:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 3:31 [PATCH] proc-based cpu affinity user interface 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2001-11-27 20:23 Matthew Dobson
2001-12-10 8:33 ` Albert D. Cahalan
2001-12-10 8:40 ` Robert Love
2001-12-10 9:37 ` Albert D. Cahalan
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=1006837709.971.6.camel@phantasy \
--to=rml@tech9.net \
--cc=anton@samba.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox