public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Dave Jones <davej@redhat.com>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH] cpu_exclusive sched domains on partial nodes temp fix
Date: Wed, 24 Aug 2005 14:07:55 -0700	[thread overview]
Message-ID: <20050824140755.4808d593.pj@sgi.com> (raw)
In-Reply-To: <20050824202133.GA10685@redhat.com>

Dave wrote:
> It does build, but I'm unable to boot test it.

Ok - thanks.

Looks like Nick might be leaning toward the simpler path of disabling
this feature (defining dynamic sched domains using exclusive cpusets)
for 2.6.13, or some such.

We'll see.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

      reply	other threads:[~2005-08-24 21:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200508240401.j7O41qlB029277@hera.kernel.org>
2005-08-24 19:06 ` [PATCH] cpu_exclusive sched domains on partial nodes temp fix Dave Jones
2005-08-24 19:13   ` Paul Jackson
2005-08-24 20:21     ` Dave Jones
2005-08-24 21:07       ` Paul Jackson [this message]

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=20050824140755.4808d593.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@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