Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754207AbbKBQWn (ORCPT ); Mon, 2 Nov 2015 11:22:43 -0500 Received: from foss.arm.com ([217.140.101.70]:51679 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753075AbbKBQWl (ORCPT ); Mon, 2 Nov 2015 11:22:41 -0500 Date: Mon, 2 Nov 2015 16:22:37 +0000 From: Catalin Marinas To: Christoph Lameter Cc: Jungseok Lee , mark.rutland@arm.com, takahiro.akashi@linaro.org, barami97@gmail.com, will.deacon@arm.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, james.morse@arm.com, tj@kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v6 2/3] percpu: add PERCPU_ATOM_SIZE for a generic percpu area setup Message-ID: <20151102162236.GB7637@e104818-lin.cambridge.arm.com> References: <1446363977-23656-1-git-send-email-jungseoklee85@gmail.com> <1446363977-23656-3-git-send-email-jungseoklee85@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1328 Lines: 27 On Mon, Nov 02, 2015 at 10:10:23AM -0600, Christoph Lameter wrote: > On Sun, 1 Nov 2015, Jungseok Lee wrote: > > > There is no room to adjust 'atom_size' now when a generic percpu area > > is used. It would be redundant to write down an architecture-specific > > setup_per_cpu_areas() in order to only change the 'atom_size'. Thus, > > this patch adds a new definition, PERCPU_ATOM_SIZE, which is PAGE_SIZE > > by default. The value could be updated if needed by architecture. > > What is atom_size? Why would you want a difference allocation size here? > The percpu area is virtually mapped regardless. So you will have > contiguous addresses even without atom_size. I haven't looked at the patch 3/3 in detail but I'm pretty sure I'll NAK the approach (and the definition of PERCPU_ATOM_SIZE), therefore rendering this patch unnecessary. IIUC, this is used to enforce some alignment of the per-CPU IRQ stack to be able to check whether the current stack is process or IRQ on exception entry. But there are other, less intrusive ways to achieve the same (e.g. x86). -- Catalin -- 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/