From: Al Viro <viro@ftp.linux.org.uk>
To: Ram <linuxram@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
akpm@osdl.org, miklos@szeredi.hu, mike@waychison.com,
bfields@fieldses.org, serue@us.ibm.com
Subject: Re: [RFC PATCH 4/10] vfs: global namespace semaphore
Date: Tue, 20 Sep 2005 07:51:42 +0100 [thread overview]
Message-ID: <20050920065142.GH7992@ftp.linux.org.uk> (raw)
In-Reply-To: <20050916182619.GA28474@RAM>
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...
next prev parent reply other threads:[~2005-09-20 6:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 18:26 [RFC PATCH 4/10] vfs: global namespace semaphore Ram
2005-09-20 6:51 ` Al Viro [this message]
2005-09-20 7:46 ` Ram Pai
2005-09-20 17:29 ` Andrew Morton
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=20050920065142.GH7992@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=akpm@osdl.org \
--cc=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=mike@waychison.com \
--cc=miklos@szeredi.hu \
--cc=serue@us.ibm.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;
as well as URLs for NNTP newsgroup(s).