From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756165AbYKTQg2 (ORCPT ); Thu, 20 Nov 2008 11:36:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753519AbYKTQgR (ORCPT ); Thu, 20 Nov 2008 11:36:17 -0500 Received: from nlpi053.sbcis.sbc.com ([207.115.36.82]:41303 "EHLO nlpi053.prodigy.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753568AbYKTQgR (ORCPT ); Thu, 20 Nov 2008 11:36:17 -0500 Date: Thu, 20 Nov 2008 10:35:05 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@quilx.com To: Rusty Russell cc: Stephen Rothwell , linux-kernel@vger.kernel.org, Andrew Morton Subject: Re: [PATCH RFC] cpu alloc cleanups and implementation improvement In-Reply-To: <200811172353.18356.rusty@rustcorp.com.au> Message-ID: References: <200811172353.18356.rusty@rustcorp.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: -2.6 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 17 Nov 2008, Rusty Russell wrote: > I've argued with Christoph that his implementation contains gratuitous > obsolescence of perfectly-good APIs; hopefully providing real patches will > give us a more useful debate. I would not mind if you would take over from here. It seems that I am into too many things again. Then you can also do the lower casing that I find inconsistent. > I hope this adds some light, As I pointed out before there are numerous semantic differences that I noted before. For the transition period where the percpu allocator has a fixed area there will be issues with an immediate conversion because the existing allocpercpu allows unbounded allocations and the cpualloc does not.