From: Dimitri Sivanich <sivanich@sgi.com>
To: devik <devik@cdi.cz>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
linux-kernel@vger.kernel.org, piggin@cyberone.com.au
Subject: Re: [PATCH] sched isolcpus=1 related OOPS in 2.6.9
Date: Fri, 3 Dec 2004 13:47:13 -0600 [thread overview]
Message-ID: <20041203194713.GB16069@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0412031907271.493-200000@devix>
On Fri, Dec 03, 2004 at 07:15:58PM +0100, devik wrote:
> A patch is attached which fixes problems with isolated
> domains for me. I hope it is correct :-) I will try on
Martin,
After a quick look, this patch looks OK (although I haven't had a chance to
test it yet). I don't know what what was intended with a default cpu_power
of 0, but I don't believe that a value of SCHED_LOAD_SCALE should negatively
affect the isolated domains (versus any other value).
Note that sched_init() does use SCHED_LOAD_SCALE as a default.
next prev parent reply other threads:[~2004-12-03 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 15:42 sched isolcpus=1 related OOPS in 2.6.9 devik
2004-12-03 16:28 ` devik
2004-12-03 17:18 ` Randy.Dunlap
2004-12-03 17:46 ` devik
2004-12-03 18:15 ` [PATCH] " devik
2004-12-03 19:47 ` Dimitri Sivanich [this message]
2004-12-03 20:21 ` devik
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=20041203194713.GB16069@sgi.com \
--to=sivanich@sgi.com \
--cc=devik@cdi.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
--cc=rddunlap@osdl.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