From: Andrea Arcangeli <andrea@suse.de>
To: Andi Kleen <andi@firstfloor.org>
Cc: "Jeffrey W. Baker" <jwbaker@acm.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: huge improvement with per-device dirty throttling
Date: Wed, 22 Aug 2007 14:47:37 +0200 [thread overview]
Message-ID: <20070822124736.GQ13915@v2.random> (raw)
In-Reply-To: <p733aybzv6e.fsf@bingen.suse.de>
On Wed, Aug 22, 2007 at 01:05:13PM +0200, Andi Kleen wrote:
> Ok perhaps the new adaptive dirty limits helps your single disk
> a lot too. But your improvements seem to be more "collateral damage" @)
>
> But if that was true it might be enough to just change the dirty limits
> to get the same effect on your system. You might want to play with
> /proc/sys/vm/dirty_*
The adaptive dirty limit is per task so it can't be reproduced with
global sysctl. It made quite some difference when I researched into it
in function of time. This isn't in function of time but it certainly
makes a lot of difference too, actually it's the most important part
of the patchset for most people, the rest is for the corner cases that
aren't handled right currently (writing to a slow device with
writeback cache has always been hanging the whole thing).
--
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:[~2007-08-22 12:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 6:37 Jeffrey W. Baker
2007-08-22 11:05 ` Andi Kleen
2007-08-22 11:09 ` Paolo Ornati
2007-08-22 12:47 ` Andrea Arcangeli [this message]
2007-09-04 9:37 ` Leroy van Logchem
2007-09-04 19:23 ` Martin Knoblauch
2007-09-06 9:50 ` Martin Knoblauch
2007-09-05 8:54 ` Martin Knoblauch
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=20070822124736.GQ13915@v2.random \
--to=andrea@suse.de \
--cc=andi@firstfloor.org \
--cc=jwbaker@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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