From: Robert Love <rml@tech9.net>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: Christoph Hellwig <hch@sgi.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] set_cpus_allowed() for 2.4
Date: 02 Dec 2002 14:10:53 -0500 [thread overview]
Message-ID: <1038856253.1221.33.camel@phantasy> (raw)
In-Reply-To: <15851.40133.974155.446342@harpo.it.uu.se>
On Mon, 2002-12-02 at 12:47, Mikael Pettersson wrote:
> I knew RH8.0 has set_cpus_allowed(), but I wanted to avoid having to check
> for being compiled in a RH-hacked kernel. LINUX_VERSION_CODE doesn't
> distinguish between standard and "with tons of vendor-specific changes" :-(
>
> I'll use your code then on stock 2.4 kernels, and work out some kludge
> for the RH case.
The code only works on the stock scheduler. It is the same interface
and has the same behavior as the O(1) scheduler version, but the code is
very very different.
If this patch is merged, you can safely use set_cpus_allowed() in either
kernel (which is the intention). But you cannot use this routine's code
on either scheduler.
Robert Love
next prev parent reply other threads:[~2002-12-02 19:03 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 23:03 [PATCH] set_cpus_allowed() for 2.4 Robert Love
2002-10-02 13:01 ` Christoph Hellwig
2002-10-02 15:00 ` Robert Love
2002-11-05 3:37 ` Christoph Hellwig
2002-11-06 15:32 ` Adrian Bunk
2002-11-07 21:42 ` Christoph Hellwig
2002-12-02 17:12 ` Mikael Pettersson
2002-12-03 0:51 ` Christoph Hellwig
2002-12-02 17:47 ` Mikael Pettersson
2002-12-02 19:10 ` Robert Love [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-03 0:26 Christoph Hellwig
2002-12-02 17:24 ` Jeff Garzik
2002-12-02 18:57 ` Robert Love
2002-12-03 0:51 ` Christoph Hellwig
2002-12-02 17:50 ` Martin J. Bligh
2002-12-02 18:50 ` Adrian Bunk
2002-12-02 19:12 ` Robert Love
2002-12-02 19:30 ` Andrew Morton
2002-12-02 19:50 ` Andrea Arcangeli
2002-12-03 20:49 ` Andrew Morton
2002-12-03 21:09 ` Martin J. Bligh
2002-12-04 0:09 ` Andrea Arcangeli
2002-12-04 0:06 ` Andrea Arcangeli
2002-12-04 0:30 ` Andrew Morton
2002-12-04 0:42 ` Andrea Arcangeli
2002-12-04 1:03 ` William Lee Irwin III
2002-12-04 9:25 ` William Lee Irwin III
2002-12-04 1:14 ` Andrew Morton
2002-12-04 1:21 ` Andrea Arcangeli
2002-12-04 2:14 ` Andrew Morton
2002-12-06 18:11 ` William Lee Irwin III
2002-12-08 13:23 ` Ingo Molnar
2002-12-08 19:56 ` Andrew Morton
2002-12-09 20:13 ` Ingo Molnar
2002-12-03 1:11 ` Christoph Hellwig
2002-12-02 18:59 ` Robert Love
2002-12-02 22:47 ` Alan Cox
2002-12-02 22:38 ` Christoph Hellwig
2002-12-02 22:41 ` Robert Love
2002-12-07 16:55 ` bill davidsen
2002-12-09 3:02 Jim Houston
2002-12-09 20:19 kernel
2002-12-13 23:08 Christoph Hellwig
2002-12-13 21:34 ` Adrian Bunk
2002-12-14 4:55 ` Christoph Hellwig
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=1038856253.1221.33.camel@phantasy \
--to=rml@tech9.net \
--cc=hch@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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