Date: Mon, 27 Oct 2008 13:55:12 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>,
       Mike Travis <travis@sgi.com>, linux-kernel@vger.kernel.org,
       Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH -tip/cpus4096-v2] cpumask: fix cpumask of
	call_function_data
Message-ID: <20081027125512.GD12461@elte.hu>
References: <49015358.9050308@ct.jp.nec.com> <200810242215.19440.rusty@rustcorp.com.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200810242215.19440.rusty@rustcorp.com.au>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 975
Lines: 28


* Rusty Russell <rusty@rustcorp.com.au> wrote:

> On Friday 24 October 2008 15:47:20 Hiroshi Shimamoto wrote:
> > From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
> 
> Ingo, because of these concerns I recommend you revert 
> d4de5ac3b5e70928c86e3e5ac311f16cbf2e9ab3 (cpumask: 
> smp_call_function_many()) for now, and apply this less contentious 
> version.

ok - applied it to tip/cpus4096-v2, thanks Rusty!

If there's any chance for this in v2.6.28 then only if we disable the 
dynamic API branch altogether [CONFIG_MAXCPUS] and keep that for 
v2.6.29. This means we'd bring in the API changes which should have 
trivial impact only - and none of the riskier changes.

Hm?

Andrew, have we missed the boat on this?

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/