From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756320AbbI1GV3 (ORCPT ); Mon, 28 Sep 2015 02:21:29 -0400 Received: from mail-la0-f54.google.com ([209.85.215.54]:33781 "EHLO mail-la0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751303AbbI1GV1 (ORCPT ); Mon, 28 Sep 2015 02:21:27 -0400 From: Rasmus Villemoes To: Rusty Russell Cc: Thomas Gleixner , Oleg Nesterov , "Paul E. McKenney" , Greg Kroah-Hartman , linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/5] kernel/cpu.c: eliminate some indirection Organization: D03 References: <1443205347-13634-1-git-send-email-linux@rasmusvillemoes.dk> <87twqgpe4y.fsf@rustcorp.com.au> X-Hashcash: 1:20:150928:linux-kernel@vger.kernel.org::8uHKkghKIi/PrDXq:0000000000000000000000000000000000itJ X-Hashcash: 1:20:150928:gregkh@linuxfoundation.org::0z3pbi/4H1hwUvOx:000000000000000000000000000000000001VTk X-Hashcash: 1:20:150928:paulmck@linux.vnet.ibm.com::SqFWruiFXcAImrAa:000000000000000000000000000000000004YyV X-Hashcash: 1:20:150928:oleg@redhat.com::GtMg0/8xSEjPTbFG:002v6N X-Hashcash: 1:20:150928:rusty@rustcorp.com.au::4mqvZtKOYzeEIl1I:00000000000000000000000000000000000000005Ozy X-Hashcash: 1:20:150928:tglx@linutronix.de::anrye8DAXX8CX7Ki:0000000000000000000000000000000000000000000AqYX Date: Mon, 28 Sep 2015 08:21:22 +0200 In-Reply-To: <87twqgpe4y.fsf@rustcorp.com.au> (Rusty Russell's message of "Sun, 27 Sep 2015 16:01:09 +0930") Message-ID: <87si5zf4il.fsf@rasmusvillemoes.dk> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Sep 27 2015, Rusty Russell wrote: > But to be clear, it has outlived its usefulness, but it was not useless. > > In particular, there used to be a debug config where 'struct cpumask' > wasn't defined, so we could catch people declaring 'struct cpumask' on > the stack (or passing by value). > > There was a plan to remove CONFIG_NR_CPUS (ie. having no compile-time > cpu limit), but it seemed overkill and was abandoned. But avoiding > 'struct cpumask' (not struct cpumask *) in the core wherever possible > was a step towards it. > > Hope that clarifies, It does, thanks! Should some of that be edited into one of the changelogs? Rasmus