All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: dino@in.ibm.com
Cc: nickpiggin@yahoo.com.au, paulus@samba.org, akpm@osdl.org,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
	torvalds@osdl.org, mingo@elte.hu, hawkes@sgi.com
Subject: Re: [PATCH 2.6.13-rc6] cpu_exclusive sched domains build fix
Date: Thu, 25 Aug 2005 15:20:04 +0000	[thread overview]
Message-ID: <20050825082004.118554de.pj@sgi.com> (raw)
In-Reply-To: <20050825144156.GA5194@in.ibm.com>

Dinakar wrote:
> I'll ack this for now until I fix the problems that I am seeing
> on ppc64

Thanks, Dinakar.

Linus - do *NOT* actually apply the literal patch that Dinakar ack'd.

 1) It's logic is backwards - arrgh.
 2) It doesn't undo the other attempt to partially disable this.
 3) It's not a formally submitted and signed off patch from me, but
    just a (useful) topic of discussion.

I have a pair of patches running through crosstool on several arch's now.

    The first patch undoes the partial disable of the cpuset to sched
    domain connection that is in 2.6.13-rc7 now.

    The second patch does what Nick and Dinakar now agree is right -
    totally disabling the ability for exclusive cpusets to define
    sched domains in 2.6.13.

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

WARNING: multiple messages have this Message-ID (diff)
From: Paul Jackson <pj@sgi.com>
To: dino@in.ibm.com
Cc: nickpiggin@yahoo.com.au, paulus@samba.org, akpm@osdl.org,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
	torvalds@osdl.org, mingo@elte.hu, hawkes@sgi.com
Subject: Re: [PATCH 2.6.13-rc6] cpu_exclusive sched domains build fix
Date: Thu, 25 Aug 2005 08:20:04 -0700	[thread overview]
Message-ID: <20050825082004.118554de.pj@sgi.com> (raw)
In-Reply-To: <20050825144156.GA5194@in.ibm.com>

Dinakar wrote:
> I'll ack this for now until I fix the problems that I am seeing
> on ppc64

Thanks, Dinakar.

Linus - do *NOT* actually apply the literal patch that Dinakar ack'd.

 1) It's logic is backwards - arrgh.
 2) It doesn't undo the other attempt to partially disable this.
 3) It's not a formally submitted and signed off patch from me, but
    just a (useful) topic of discussion.

I have a pair of patches running through crosstool on several arch's now.

    The first patch undoes the partial disable of the cpuset to sched
    domain connection that is in 2.6.13-rc7 now.

    The second patch does what Nick and Dinakar now agree is right -
    totally disabling the ability for exclusive cpusets to define
    sched domains in 2.6.13.

-- 
                  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-25 15:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-23  8:04 [PATCH 2.6.13-rc6] cpu_exclusive sched domains on partial nodes temp fix Paul Jackson
2005-08-23  8:04 ` Paul Jackson
2005-08-23  8:10 ` Ingo Molnar
2005-08-23  8:10   ` Ingo Molnar
2005-08-23 15:07 ` Dinakar Guniguntala
2005-08-23 15:19   ` Dinakar Guniguntala
2005-08-24  0:19 ` John Hawkes
2005-08-24  0:19   ` John Hawkes
2005-08-24 11:15 ` [PATCH 2.6.13-rc6] cpu_exclusive sched domains build fix Paul Jackson
2005-08-24 11:15   ` Paul Jackson
2005-08-24 11:26   ` Dinakar Guniguntala
2005-08-24 11:38     ` Dinakar Guniguntala
2005-08-24 11:46     ` Paul Jackson
2005-08-24 11:46       ` Paul Jackson
2005-08-24 12:01       ` Nick Piggin
2005-08-24 12:01         ` Nick Piggin
2005-08-24 20:31         ` Paul Jackson
2005-08-24 20:31           ` Paul Jackson
2005-08-25  0:02           ` Nick Piggin
2005-08-25  0:02             ` Nick Piggin
2005-08-25  0:57             ` Paul Jackson
2005-08-25  0:57               ` Paul Jackson
2005-08-25 14:41           ` Dinakar Guniguntala
2005-08-25 14:53             ` Dinakar Guniguntala
2005-08-25 15:20             ` Paul Jackson [this message]
2005-08-25 15:20               ` Paul Jackson
2005-08-24 16:09     ` John Hawkes
2005-08-24 16:09       ` John Hawkes

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=20050825082004.118554de.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=akpm@osdl.org \
    --cc=dino@in.ibm.com \
    --cc=hawkes@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nickpiggin@yahoo.com.au \
    --cc=paulus@samba.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 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.