Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759420Ab0D3TFj (ORCPT ); Fri, 30 Apr 2010 15:05:39 -0400 Received: from www.tglx.de ([62.245.132.106]:47176 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933390Ab0D3TFC (ORCPT ); Fri, 30 Apr 2010 15:05:02 -0400 Date: Fri, 30 Apr 2010 21:04:42 +0200 (CEST) From: Thomas Gleixner To: Peter P Waskiewicz Jr cc: "davem@davemloft.net" , "arjan@linux.jf.intel.com" , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH linux-next v2 1/2] irq: Add CPU mask affinity hint In-Reply-To: Message-ID: References: <20100430085150.4630.46790.stgit@ppwaskie-hc2.jf.intel.com> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1460 Lines: 35 On Fri, 30 Apr 2010, Peter P Waskiewicz Jr wrote: > On Fri, 30 Apr 2010, Thomas Gleixner wrote: > > > +extern int irq_register_affinity_hint(unsigned int irq, > > > + const struct cpumask *m); > > > > I think we can do with a single funtion irq_set_affinity_hint() and > > let the caller set the pointer to NULL. > > Ok, I've been running into some issues. If CONFIG_CPUMASK_OFFSTACK is not > set, then cpumask_var_t structs are single-element arrays that cannot be > NULL'd out. I'm pretty sure I need to keep the unregister part of the API. > Thoughts? extern int irq_set_affinity_hint(unsigned int irq, const struct cpumask *m); So why should calling irq_set_affinity_hint(irqnr, NULL) not work ? > I just looked at the original show_affinity function, and it does not grab > desc->lock before copying mask out of desc. Should I follow that model, or > should I fix that function to honor desc->lock? desc->affinity can only race against something changing the affinity bits, so that just might return some random data. In the hint case the irq could be shut down and the affinity hint could be freed while you are accessing it. Not a good idea :) Thanks, tglx -- 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/