[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <C5F7F0FE.DED5%jos@hyves.nl>
Date: Tue, 31 Mar 2009 16:10:38 +0200
From: Jos Houtman <jos@...es.nl>
To: Wu Fengguang <fengguang.wu@...el.com>
CC: Nick Piggin <nickpiggin@...oo.com.au>,
<linux-kernel@...r.kernel.org>, Jeff Layton <jlayton@...hat.com>,
Dave Chinner <david@...morbit.com>,
<linux-fsdevel@...r.kernel.org>, <jens.axboe@...cle.com>,
<akpm@...ux-foundation.org>, <hch@...radead.org>,
<linux-nfs@...r.kernel.org>
Subject: Re: Page Cache writeback too slow, SSD/noop scheduler/ext2
>> 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.
>
> I noticed this annoying writes-starve-reads problem too. I'll look into it.
Thanks
>
>> Is there anything I can do about this behaviour by creating a better
>> interleaving of the reads and writes?
>
> I guess it should be handled in the generic block io layer. Once we
> solved the writes-starve-reads problem, the bursty-writeback behavior
> becomes a no-problem for SSD.
Yeah this was the part where I figured the io-schedulers kicked in, but
obviously I was wrong :P.
If I can do anything more to help this along, let me know.
Thanks
Jos
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists