From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264313AbUBKMUl (ORCPT ); Wed, 11 Feb 2004 07:20:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264329AbUBKMUk (ORCPT ); Wed, 11 Feb 2004 07:20:40 -0500 Received: from mail.shareable.org ([81.29.64.88]:17281 "EHLO mail.shareable.org") by vger.kernel.org with ESMTP id S264313AbUBKMUj (ORCPT ); Wed, 11 Feb 2004 07:20:39 -0500 Date: Wed, 11 Feb 2004 12:20:31 +0000 From: Jamie Lokier To: Ingo Molnar Cc: Andrew Morton , Alexander Viro , Linus Torvalds , linux-kernel@vger.kernel.org Subject: Re: open-scale-2.6.2-A0 Message-ID: <20040211122031.GC15127@mail.shareable.org> References: <20040211115828.GA13868@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040211115828.GA13868@elte.hu> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Ingo Molnar wrote: > i've attached an obvious scalability improvement for write()s. We in > essence used a system-global lock for every open(WRITE) - argh! I wonder if the "rip the second arsehole" is there for a reason. Does this scalability improvement make any measured difference in any conceivable application, or is it just making struct inode larger? -- Jamie