From: Olaf Kirch <okir@suse.de>
To: nfs@lists.sourceforge.net
Subject: Re: nfsd write throughput
Date: Tue, 3 Aug 2004 12:52:38 +0200 [thread overview]
Message-ID: <20040803105238.GH21365@suse.de> (raw)
In-Reply-To: <20040803103213.GE21365@suse.de>
On Tue, Aug 03, 2004 at 12:32:14PM +0200, Olaf Kirch wrote:
> I'm wondering what could happen if we change nfsd_sync to not take the
> i_sem at all... I'll talk to a few VFS folks around here and try to find out.
Just for fun, I changed nfsd_sync to not take i_sem, and the
performance gain was about halfway inbetween the unmodified
nfsd and the one with the flushfast hack.
I think the reason this isn't better than flushfast is this: when several
commit calls for the same file come in (and as I mentioned, the Linux
client does send up to 80 commits per second), we end up with all nfsd
threads handling one commit, sitting in filemap_fdatawait or fsync,
waiting for the same file to be flushed.
Olaf
--
Olaf Kirch | The Hardware Gods hate me.
okir@suse.de |
---------------+
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-08-03 10:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 16:24 nfsd write throughput Olaf Kirch
2004-08-03 2:10 ` Greg Banks
2004-08-03 6:02 ` Olaf Kirch
2004-08-03 7:55 ` Greg Banks
2004-08-03 8:09 ` Olaf Kirch
2004-08-03 8:28 ` Greg Banks
2004-08-03 10:32 ` Olaf Kirch
2004-08-03 10:52 ` Olaf Kirch [this message]
2004-08-03 11:24 ` Greg Banks
2004-08-03 13:26 ` Olaf Kirch
2004-08-03 2:23 ` Neil Brown
-- strict thread matches above, loose matches on Subject: below --
2004-08-04 0:10 Bruce Allan
2004-08-04 8:18 ` Greg Banks
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=20040803105238.GH21365@suse.de \
--to=okir@suse.de \
--cc=nfs@lists.sourceforge.net \
/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.