From: Lee Revell <rlrevell@joe-job.com>
To: Peter Staubach <staubach@redhat.com>
Cc: steve <lingxiang@huawei.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"zhangtiger@huawei.com" <zhangtiger@huawei.com>
Subject: Re: why nfs server delay 10ms in nfsd_write()?
Date: Thu, 19 May 2005 09:59:00 -0400 [thread overview]
Message-ID: <1116511140.21587.4.camel@mindpipe> (raw)
In-Reply-To: <428C8C32.2030803@redhat.com>
On Thu, 2005-05-19 at 08:53 -0400, Peter Staubach wrote:
> There are certainly many others way to get gathering, without adding an
> artificial delay. There are already delay slots built into the code
> which could
> be used to trigger the gathering, so with a little bit different
> architecture, the
> performance increases could be achieved.
>
> Some implementations actually do write gathering with NFSv3, even. Is
> this interesting enough to play with? I suspect that just doing the
> work for
> NFSv2 is not...
Also, how do you explain the big performance hit that steve observed?
Write gathering is supposed to help performance, but it's a big loss on
his test...
Lee
next prev parent reply other threads:[~2005-05-19 13:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 2:46 why nfs server delay 10ms in nfsd_write()? steve
2005-05-19 3:08 ` Trond Myklebust
2005-05-19 3:13 ` Lee Revell
2005-05-19 12:53 ` Peter Staubach
2005-05-19 13:26 ` Trond Myklebust
2005-05-19 13:41 ` Peter Staubach
2005-05-19 13:59 ` Lee Revell [this message]
2005-05-19 14:10 ` Peter Staubach
2005-05-19 14:13 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2005-05-20 10:44 steve
2005-05-20 13:05 ` Peter Staubach
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=1116511140.21587.4.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=lingxiang@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=staubach@redhat.com \
--cc=zhangtiger@huawei.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.