From: Al Viro <viro@ftp.linux.org.uk>
To: Avi Kivity <avi@argo.co.il>
Cc: Josef Sipek <jsipek@fsl.cs.sunysb.edu>,
lkml@pengaru.com, linux-kernel@vger.kernel.org
Subject: Re: rename() contention (BUG?)
Date: Thu, 26 Oct 2006 20:22:20 +0100 [thread overview]
Message-ID: <20061026192219.GL29920@ftp.linux.org.uk> (raw)
In-Reply-To: <454101D6.9050004@argo.co.il>
On Thu, Oct 26, 2006 at 08:43:34PM +0200, Avi Kivity wrote:
> The changes make the mutex more efficient, but won't decrease the
> contention. It seems that all renames in one filesystem are serialized,
> and if the renames require I/O (which is certainly the case with nfs),
> rename throughput is severely limited.
They are, and for a good reason. For details see
Documentation/filesystems/directory-locking.
next prev parent reply other threads:[~2006-10-26 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 20:56 rename() contention (BUG?) lkml
2006-10-25 21:13 ` Josef Sipek
2006-10-26 18:43 ` Avi Kivity
2006-10-26 19:22 ` Al Viro [this message]
2006-10-26 21:19 ` Avi Kivity
2006-10-26 21:37 ` Al Viro
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=20061026192219.GL29920@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=avi@argo.co.il \
--cc=jsipek@fsl.cs.sunysb.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@pengaru.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox