Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030411AbWARWW0 (ORCPT ); Wed, 18 Jan 2006 17:22:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932564AbWARWW0 (ORCPT ); Wed, 18 Jan 2006 17:22:26 -0500 Received: from kanga.kvack.org ([66.96.29.28]:52186 "EHLO kanga.kvack.org") by vger.kernel.org with ESMTP id S932561AbWARWWZ (ORCPT ); Wed, 18 Jan 2006 17:22:25 -0500 Date: Wed, 18 Jan 2006 17:18:11 -0500 From: Benjamin LaHaise To: "David S. Miller" Cc: stern@rowland.harvard.edu, akpm@osdl.org, sekharan@us.ibm.com, kaos@sgi.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/8] Notifier chain update Message-ID: <20060118221811.GJ16285@kvack.org> References: <20060118220122.GH16285@kvack.org> <20060118.141841.87446048.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060118.141841.87446048.davem@davemloft.net> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 671 Lines: 16 On Wed, Jan 18, 2006 at 02:18:41PM -0800, David S. Miller wrote: > If you need to block, take a mutex around the notifier calls. > (I nearly typed semaphore there, sorry Ingo! :-) I'm arguing against adding the mutex. We don't need things like munmap() on every cpu doing a down_read() on system wide semaphore. -ben -- "You know, I've seen some crystals do some pretty trippy shit, man." Don't Email: . - 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/