public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andi Kleen <ak@muc.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Move domain setup and add dual core support.
Date: Tue, 14 Sep 2004 23:38:50 +1000	[thread overview]
Message-ID: <4146F46A.6070800@yahoo.com.au> (raw)
In-Reply-To: <20040914132055.GA79737@muc.de>

Andi Kleen wrote:
> On Tue, Sep 14, 2004 at 11:00:48PM +1000, Nick Piggin wrote:
> 
>>Andi Kleen wrote:
>>
>>
>>>Patch is for 2.6.9rc1-bk19. It's much smaller than it looks,
>>>most of it is just moving code from sched.c to sched-domains.h
>>>
>>
>>OK, I guess this should be alright... but it will clash badly
>>with the stuff in -mm, which really needs to get in.
> 
> 
> Ok, I will redo it.
> 
> But I would like to have the CMP patch soon in mainline for 2.6.9. Are 
> the patches in mm scheduled to be soon in mainline? 

I hope so for 2.6.9. Not too sure of the plans, but if they prove
stable early on in -mm, I think there may be enough time to get them
in for 2.6.9

> 
>>And your patch will be much smaller because most of the moving
>>is done for you.
> 
> 
> Where is it moved to? 
> 

include/linux/sched.h

I know we've been trying to move stuff *out* of there, but this is
something that actually fits. On the other hand, it is not really
going to be used by more than a few files outside sched.c, so maybe
it could go to its own file if anyone felt strongly about it.

  reply	other threads:[~2004-09-14 13:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-13 14:28 [PATCH] Move domain setup and add dual core support Andi Kleen
2004-09-14 13:00 ` Nick Piggin
2004-09-14 13:20   ` Andi Kleen
2004-09-14 13:38     ` Nick Piggin [this message]
2004-09-14 15:49       ` Andi Kleen

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=4146F46A.6070800@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=ak@muc.de \
    --cc=akpm@osdl.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