From: Judith Flo Gaya <jflo@imppc.org>
To: Jim Rees <rees@umich.edu>
Cc: Chuck Lever <chuck.lever@oracle.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: problem with nfs latency during high IO
Date: Wed, 16 Mar 2011 17:52:57 +0100 [thread overview]
Message-ID: <4D80EAE9.6000603@imppc.org> (raw)
In-Reply-To: <20110316153129.GB12187@merit.edu>
THanks a lot to both for your suggestions and help.
I already filed a bug [1] to bugzilla.
j
[1] https://bugzilla.redhat.com/show_bug.cgi?id=688232
On 03/16/2011 04:31 PM, Jim Rees wrote:
> Jim Rees wrote:
>
> I think 5 is the minimum for dirty_ratio, although this doesn't seem to be
> documented anywhere. If you want to set it lower, you have to use
> dirty_bytes instead of dirty_ratio.
>
> Never mind, I just looked at the code and the 5% limit seems to have been
> removed later. Last time I looked at this code was 3 years ago.
--
Judith Flo Gaya
Systems Administrator IMPPC
e-mail: jflo@imppc.org
Tel (+34) 93 554-3079
Fax (+34) 93 465-1472
Institut de Medicina Predictiva i Personalitzada del Càncer
Crta Can Ruti, Camí de les Escoles s/n
08916 Badalona, Barcelona,
Spain
http://www.imppc.org
next prev parent reply other threads:[~2011-03-16 16:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 12:58 problem with nfs latency during high IO Judith Flo Gaya
2011-03-15 16:24 ` Chuck Lever
2011-03-15 17:25 ` Judith Flo Gaya
2011-03-15 18:03 ` Chuck Lever
2011-03-15 18:15 ` Chuck Lever
2011-03-17 1:21 ` Harshula Jayasuriya
2011-03-15 21:33 ` Judith Flo Gaya
2011-03-15 21:28 ` Chuck Lever
2011-03-15 21:58 ` Judith Flo Gaya
2011-03-15 22:10 ` Chuck Lever
2011-03-16 11:45 ` Judith Flo Gaya
2011-03-16 13:24 ` Chuck Lever
2011-03-16 13:42 ` peter.staubach
2011-03-16 15:18 ` Jim Rees
2011-03-16 15:31 ` Jim Rees
2011-03-16 16:52 ` Judith Flo Gaya [this message]
2011-03-16 23:51 ` Simon Kirby
-- strict thread matches above, loose matches on Subject: below --
2011-03-15 16:25 Judith Flo Gaya
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=4D80EAE9.6000603@imppc.org \
--to=jflo@imppc.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
/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.