Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751284Ab0F1Jbl (ORCPT ); Mon, 28 Jun 2010 05:31:41 -0400 Received: from ozlabs.org ([203.10.76.45]:33972 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750992Ab0F1Jbj (ORCPT ); Mon, 28 Jun 2010 05:31:39 -0400 From: Rusty Russell To: Christoph Lameter Subject: Re: [PATCH 2/5] cpumask: make task_struct.cpus_allowed a cpumask_var_t Date: Mon, 28 Jun 2010 19:01:26 +0930 User-Agent: KMail/1.13.2 (Linux/2.6.32-22-generic; KDE/4.4.2; i686; ; ) Cc: Ingo Molnar , linux-kernel@vger.kernel.org, Russell King , Bryan Wu , Tony Luck , Ralf Baechle , Benjamin Herrenschmidt , Paul Mundt , "David S. Miller" , Arnd Bergmann , anton@samba.org, KOSAKI Motohiro , Mike Travis References: <201006252233.40481.rusty@rustcorp.com.au> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201006281901.27517.rusty@rustcorp.com.au> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1075 Lines: 26 On Sat, 26 Jun 2010 01:30:25 am Christoph Lameter wrote: > On Fri, 25 Jun 2010, Rusty Russell wrote: > > > Even better would be to point to the fixed "one cpu" and "all cpus" > > masks where possible, and make a copy when setting it to something > > else. But you'd have to track down those naughty places which frob it > > directly... > > Put it into a read only segment? Well, I was thinking of an audit as the first step :) > What is the estimated performance impact of adding a level of indirection > (and a potential cache miss) to a number of critical code paths? Unknown. Originally, I moved the mask to the end of the struct (so we could under-allocate for the CPUMASK_OFFSTACK nr_cpu_ids < NR_CPUS case), but Ingo didn't want to change the struct for the non-CPUMASK_OFFSTACK case. Measurements welcome... Rusty. -- 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/