From: Andi Kleen <andi@firstfloor.org>
To: "Jeffrey W. Baker" <jwbaker@acm.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: huge improvement with per-device dirty throttling
Date: 22 Aug 2007 13:05:13 +0200 [thread overview]
Message-ID: <p733aybzv6e.fsf@bingen.suse.de> (raw)
In-Reply-To: <1187764638.6869.17.camel@hannibal>
"Jeffrey W. Baker" <jwbaker@acm.org> writes:
>
> My system is a Core 2 Duo, 2GB, single SATA disk.
Hmm, I thought the patch was only supposed to make a real difference
if you have multiple devices? But you only got a single disk.
At least that was the case it was supposed to fix: starvation of fast
devices from slow devices.
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_*
-Andi
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: "Jeffrey W. Baker" <jwbaker@acm.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: huge improvement with per-device dirty throttling
Date: 22 Aug 2007 13:05:13 +0200 [thread overview]
Message-ID: <p733aybzv6e.fsf@bingen.suse.de> (raw)
In-Reply-To: <1187764638.6869.17.camel@hannibal>
"Jeffrey W. Baker" <jwbaker@acm.org> writes:
>
> My system is a Core 2 Duo, 2GB, single SATA disk.
Hmm, I thought the patch was only supposed to make a real difference
if you have multiple devices? But you only got a single disk.
At least that was the case it was supposed to fix: starvation of fast
devices from slow devices.
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_*
-Andi
--
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 10:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 6:37 huge improvement with per-device dirty throttling Jeffrey W. Baker
2007-08-22 6:37 ` Jeffrey W. Baker
2007-08-22 11:05 ` Andi Kleen [this message]
2007-08-22 11:05 ` Andi Kleen
2007-08-22 11:09 ` Paolo Ornati
2007-08-22 11:09 ` Paolo Ornati
2007-08-22 12:47 ` Andrea Arcangeli
2007-08-22 12:47 ` Andrea Arcangeli
2007-09-04 9:37 ` Leroy van Logchem
2007-09-04 9:37 ` Leroy van Logchem
2007-09-04 19:23 ` Martin Knoblauch
2007-09-04 19:23 ` Martin Knoblauch
2007-09-06 9:50 ` Martin Knoblauch
2007-09-06 9:50 ` Martin Knoblauch
2007-09-05 8:54 ` Martin Knoblauch
2007-09-05 8:54 ` Martin Knoblauch
-- strict thread matches above, loose matches on Subject: below --
2007-08-22 11:31 Al Boldi
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=p733aybzv6e.fsf@bingen.suse.de \
--to=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 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.