From: Christoph Hellwig <hch@infradead.org>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: Marcelo Tossati <marcelo@conectiva.com.br>,
linux-fsdevel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Andrea Arcangeli <andrea@suse.de>,
Dave Kleikamp <shaggy@austin.ibm.com>,
Nathan Scott <nathans@sgi.com>, Chris Mason <mason@suse.com>,
Tim Shimmin <tes@sgi.com>, Jeff Mahoney <jeffm@suse.com>,
Steve Best <sbest@us.ibm.com>
Subject: Re: xattr iops locking improvement
Date: Mon, 7 Jul 2003 18:57:01 +0100 [thread overview]
Message-ID: <20030707185701.A6224@infradead.org> (raw)
In-Reply-To: <200307071948.04703.agruen@suse.de>; from agruen@suse.de on Mon, Jul 07, 2003 at 07:48:04PM +0200
On Mon, Jul 07, 2003 at 07:48:04PM +0200, Andreas Gruenbacher wrote:
> Hi Marcelo,
>
> Andrew Morton has found that taking i_sem for all xattr iops leads to lock
> contention. Particularly annoying is that writers can block operations like
> `ls -l' because both need i_sem. We have bene working on a fix for 2.4 and
> 2.5. The solution is a series of patches that are in Andrew's current tree,
> and have been sent to Linus. I will also shortly put them on
> http://acl.bestbits.at/.
~o(/me remembers having argued for no VFS-level locking on them a while ago)
Can we please get rid of the i_sem on the other two operations, and finally
move all locking to the implementation?
prev parent reply other threads:[~2003-07-07 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-07 17:48 xattr iops locking improvement Andreas Gruenbacher
2003-07-07 17:57 ` Christoph Hellwig [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030707185701.A6224@infradead.org \
--to=hch@infradead.org \
--cc=agruen@suse.de \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=jeffm@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mason@suse.com \
--cc=nathans@sgi.com \
--cc=sbest@us.ibm.com \
--cc=shaggy@austin.ibm.com \
--cc=tes@sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.