From: "Xin Zhao" <uszhaoxin@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: Why must NFS access metadata in synchronous mode?
Date: Thu, 1 Jun 2006 00:04:11 -0400 [thread overview]
Message-ID: <4ae3c140605312104m441ca006j784a93354456faf8@mail.gmail.com> (raw)
Until kernel 2.6.16, I think NFS still access metadata synchronously,
which may impact performance significantly. Several years ago, paper
"metadata update performance in file systems" already suggested using
asynchronous mode in metadata access.
I am curious why NFS does not adopt this suggestion? Can someone explain this?
Thanks!
Xin
next reply other threads:[~2006-06-01 4:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 4:04 Xin Zhao [this message]
2006-06-01 5:55 ` Why must NFS access metadata in synchronous mode? Trond Myklebust
2006-06-01 16:27 ` Xin Zhao
2006-06-01 17:26 ` Trond Myklebust
2006-06-02 3:42 ` Can Sar
2006-06-02 4:06 ` Trond Myklebust
2006-06-01 21:40 ` Andreas Dilger
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=4ae3c140605312104m441ca006j784a93354456faf8@mail.gmail.com \
--to=uszhaoxin@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).