From: Jos Houtman <jos@hyves.nl>
To: Jos Houtman <jos@hyves.nl>, Wu Fengguang <fengguang.wu@intel.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
<linux-kernel@vger.kernel.org>, Jeff Layton <jlayton@redhat.com>,
Dave Chinner <david@fromorbit.com>,
<linux-fsdevel@vger.kernel.org>, <jens.axboe@oracle.com>,
<akpm@linux-foundation.org>, <hch@infradead.org>,
<linux-nfs@vger.kernel.org>
Subject: Re: Page Cache writeback too slow, SSD/noop scheduler/ext2
Date: Tue, 31 Mar 2009 14:16:52 +0200 [thread overview]
Message-ID: <C5F7D654.DE6F%jos@hyves.nl> (raw)
In-Reply-To: <C5F6B627.D9D0%jos@hyves.nl>
>
> Next to that I was wondering if there are any plans to make sure that not
> all dirty-files are written back in the same interval.
>
> In my case all database files are written back each 30 seconds, while I
> would prefer them to be more divided over the interval.
There another question I have: does the writeback go through the io
scheduler? Because no matter the io scheduler or the tuning done, the
writeback algorithm totally starves the reads.
See the url below for an example with CFQ, but deadline or noop all show
this behaviour:
http://94.100.113.33/535450001-535500000/535451701-535451800/535451800_6_L7g
t.jpeg
Is there anything I can do about this behaviour by creating a better
interleaving of the reads and writes?
Jos
next prev parent reply other threads:[~2009-03-31 12:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C5EC2B99.C3B3%jos@hyves.nl>
[not found] ` <200903250148.53644.nickpiggin@yahoo.com.au>
2009-03-25 5:26 ` Page Cache writeback too slow, SSD/noop scheduler/ext2 Wu Fengguang
2009-03-27 16:59 ` Jos Houtman
2009-03-29 2:32 ` Wu Fengguang
2009-03-30 16:47 ` Jos Houtman
2009-03-31 0:28 ` Wu Fengguang
2009-03-31 12:16 ` Jos Houtman [this message]
2009-03-31 12:31 ` Wu Fengguang
2009-03-31 14:10 ` Jos Houtman
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=C5F7D654.DE6F%jos@hyves.nl \
--to=jos@hyves.nl \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=fengguang.wu@intel.com \
--cc=hch@infradead.org \
--cc=jens.axboe@oracle.com \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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