From: Peter Zijlstra <peterz@infradead.org>
To: david@lang.hm
Cc: Jan Kara <jack@suse.cz>,
Linus Torvalds <torvalds@linux-foundation.org>,
Chris Mason <chris.mason@oracle.com>,
David Miller <davem@davemloft.net>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, npiggin@suse.de
Subject: Re: Increase dirty_ratio and dirty_background_ratio?
Date: Fri, 09 Jan 2009 22:34:31 +0100 [thread overview]
Message-ID: <1231536871.29452.1.camel@twins> (raw)
In-Reply-To: <alpine.DEB.1.10.0901091420190.3525@asgard.lang.hm>
On Fri, 2009-01-09 at 14:31 -0800, david@lang.hm wrote:
> for that matter, it's not getting to where it makes sense to have wildly
> different storage on a machine
>
> 10's of GB of SSD for super-fast read-mostly
> 100's of GB of high-speed SCSI for fast writes
> TB's of SATA for high capacity
>
> does it make sense to consider tracking the dirty pages per-destination so
> that in addition to only having one process writing to the drive at a time
> you can also allow for different amounts of data to be queued per device?
>
> on a machine with 10's of GB of ram it becomes possible to hit the point
> where at one point you could have the entire SSD worth of data queued up
> to write, and at another point have the same total amount of data queued
> for the SATA storage and it's a fraction of a percent of the size of the
> storage.
That's exactly what we do today. Dirty pages are tracked per backing
device and the writeback cache size is proportionally divided based on
recent write speed ratios of the devices.
--
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:[~2009-01-09 21:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090107154517.GA5565@duck.suse.cz>
2009-01-07 16:25 ` Peter Zijlstra
2009-01-07 16:39 ` Linus Torvalds
2009-01-07 20:51 ` David Miller
2009-01-08 11:02 ` Andrew Morton
2009-01-08 16:24 ` David Miller
2009-01-08 16:48 ` Linus Torvalds
2009-01-08 16:55 ` Chris Mason
2009-01-08 17:05 ` Linus Torvalds
2009-01-08 19:57 ` Jan Kara
2009-01-08 20:01 ` David Miller
2009-01-09 18:02 ` Jan Kara
2009-01-09 19:00 ` Andrew Morton
2009-01-09 19:07 ` Chris Mason
2009-01-09 22:31 ` david
2009-01-09 21:34 ` Peter Zijlstra [this message]
2009-01-14 3:29 ` Nick Piggin
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=1231536871.29452.1.camel@twins \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=davem@davemloft.net \
--cc=david@lang.hm \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=torvalds@linux-foundation.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