From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [RFC PATCH 4/10] vfs: global namespace semaphore Date: Tue, 20 Sep 2005 10:29:00 -0700 Message-ID: <20050920102900.046b128f.akpm@osdl.org> References: <20050916182619.GA28474@RAM> <20050920065142.GH7992@ftp.linux.org.uk> <1127202362.10061.16.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: viro@ftp.linux.org.uk, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, miklos@szeredi.hu, mike@waychison.com, bfields@fieldses.org, serue@us.ibm.com Return-path: Received: from smtp.osdl.org ([65.172.181.4]:22425 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S932717AbVITR3z (ORCPT ); Tue, 20 Sep 2005 13:29:55 -0400 To: Ram Pai In-Reply-To: <1127202362.10061.16.camel@localhost> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Ram Pai wrote: > > On Mon, 2005-09-19 at 23:51, Al Viro wrote: > > On Fri, Sep 16, 2005 at 11:26:19AM -0700, Ram wrote: > > > This patch removes the per-namespace semaphore in favor of a global > > > semaphore. This can have an effect on namespace scalability. > > > > ... and #2 uses that semaphore... > > Patch #2, uses the global semaphore. Yes that patch would'nt have > compiled without patch #4, because the global semaphore got defined only > in the patch #4. > Ordinarily that doesn't matter much. But if you're doing a `git bisect' and you happen to land in the middle of a patch series at a point where it doesn't compile or run, it can ruin your whole day.