LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, neilb@suse.de, dgc@sgi.com,
	tomoki.sekiyama.qu@hitachi.com, a.p.zijlstra@chello.nl
Subject: [RFC][PATCH 0/6] per device dirty throttling
Date: Mon, 19 Mar 2007 16:57:37 +0100	[thread overview]
Message-ID: <20070319155737.653325176@programming.kicks-ass.net> (raw)

This patch-set implements per device dirty page throttling. Which should solve
the problem we currently have with one device hogging the dirty limit.

Preliminary testing shows good results:

mem=128M

time (dd if=/dev/zero of=/mnt/<dev>/zero bs=4096 count=$((1024*1024/4)); sync)

1GB to disk

real    0m33.074s       0m34.596s       0m33.387s
user    0m0.147s        0m0.163s        0m0.142s
sys     0m7.872s        0m8.409s        0m8.395s

1GB to usb-flash

real    3m21.170s       3m15.512s       3m23.889s
user    0m0.135s        0m0.146s        0m0.127s
sys     0m7.327s        0m7.328s        0m7.342s


2.6.20 device vs device

1GB disk vs disk

real    1m30.736s       1m16.133s       1m42.068s
user    0m0.204s        0m0.167s        0m0.222s
sys     0m10.438s       0m7.958s        0m10.599s

1GB usb-flash vs background disk

N/A 30m+

1GB disk vs background usb-flash

real    4m0.687s        2m20.145s       4m12.923s
user    0m0.173s        0m0.185s        0m0.161s
sys     0m8.227s        0m8.581s        0m8.345s


2.6.20-writeback

1GB disk vs disk

real    0m36.696s	0m40.837s	0m38.679s
user    0m0.161s	0m0.148s	0m0.160s
sys     0m8.240s	0m8.068s	0m8.174s

1GB usb-flash vs background disk

real    3m37.464s	3m49.720s	4m5.805s
user    0m0.167s	0m0.166s	0m0.149s
sys     0m7.195s	0m7.281s	0m7.199s

1GB disk vs background usb-flash

real    0m41.585s	0m30.888s	0m34.493s
user    0m0.161s	0m0.167s	0m0.162s
sys     0m7.826s	0m7.807s	0m7.821s



             reply	other threads:[~2007-03-19 17:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-19 15:57 Peter Zijlstra [this message]
2007-03-19 15:57 ` [RFC][PATCH 1/6] mm: scalable bdi statistics counters Peter Zijlstra
2007-03-19 15:57 ` [RFC][PATCH 2/6] mm: count dirty pages per BDI Peter Zijlstra
2007-03-19 15:57 ` [RFC][PATCH 3/6] mm: count writeback " Peter Zijlstra
2007-03-19 15:57 ` [RFC][PATCH 4/6] mm: count unstable " Peter Zijlstra
2007-03-19 15:57 ` [RFC][PATCH 5/6] mm: per device dirty threshold Peter Zijlstra
2007-03-19 15:57 ` [RFC][PATCH 6/6] mm: expose BDI statistics in sysfs Peter Zijlstra
2007-03-19 18:29 ` [RFC][PATCH 0/6] per device dirty throttling Peter Zijlstra
2007-03-19 21:48 ` [RFC][PATCH 7/6] assorted fixes Peter Zijlstra
2007-03-20  7:47 ` [RFC][PATCH 0/6] per device dirty throttling David Chinner
2007-03-20  8:08   ` Peter Zijlstra
2007-03-20  9:38     ` David Chinner
2007-03-20  9:45       ` Peter Zijlstra
2007-03-20 15:38         ` Peter Zijlstra

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=20070319155737.653325176@programming.kicks-ass.net \
    --to=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=dgc@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=neilb@suse.de \
    --cc=tomoki.sekiyama.qu@hitachi.com \
    --subject='Re: [RFC][PATCH 0/6] per device dirty throttling' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).