From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Zan Lynx <zlynx@acm.org>
Cc: kosaki.motohiro@jp.fujitsu.com, lwoodman@redhat.com,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Nick Piggin <npiggin@suse.de>,
Jan Kara <jack@suse.cz>
Subject: Re: RFC: dirty_ratio back to 40%
Date: Fri, 21 May 2010 10:11:59 +0900 (JST) [thread overview]
Message-ID: <20100521100943.1E4D.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <4BF5D875.3030900@acm.org>
> > So, I'd prefer to restore the default rather than both Redhat and SUSE apply exactly
> > same distro specific patch. because we can easily imazine other users will face the same
> > issue in the future.
>
> On desktop systems the low dirty limits help maintain interactive feel.
> Users expect applications that are saving data to be slow. They do not
> like it when every application in the system randomly comes to a halt
> because of one program stuffing data up to the dirty limit.
really?
Do you mean our per-task dirty limit wouldn't works?
If so, I think we need fix it. IOW sane per-task dirty limitation seems independent issue
from per-system dirty limit.
> The cause and effect for the system slowdown is clear when the dirty
> limit is low. "I saved data and now the system is slow until it is
> done." When the dirty page ratio is very high, the cause and effect is
> disconnected. "I was just web surfing and the system came to a halt."
>
> I think we should expect server admins to do more tuning than desktop
> users, so the default limits should stay low in my opinion.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-05-21 1:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 11:20 Larry Woodman
2010-05-20 12:29 ` Heinz Diehl
2010-05-20 13:47 ` Richard Kennedy
2010-05-20 23:48 ` KOSAKI Motohiro
2010-05-21 0:48 ` Zan Lynx
2010-05-21 1:11 ` KOSAKI Motohiro [this message]
2010-05-21 16:00 ` Jan Kara
2010-05-24 19:50 ` Ric Wheeler
2010-05-21 15:50 ` Jan Kara
2010-05-21 6:18 ` David Miller
2010-06-08 18:49 ` Christoph Hellwig
2010-06-08 19:01 ` Larry Woodman
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=20100521100943.1E4D.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lwoodman@redhat.com \
--cc=npiggin@suse.de \
--cc=zlynx@acm.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