[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090905132653.GH24516@shareable.org>
Date: Sat, 5 Sep 2009 14:26:53 +0100
From: Jamie Lokier <jamie@...reable.org>
To: Richard Kennedy <richard@....demon.co.uk>
Cc: Jens Axboe <jens.axboe@...cle.com>, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, chris.mason@...cle.com,
david@...morbit.com, hch@...radead.org, tytso@....edu,
akpm@...ux-foundation.org, jack@...e.cz
Subject: Re: [PATCH 8/8] vm: Add an tuning knob for vm.max_writeback_mb
Richard Kennedy wrote:
> I've been testing this & it works pretty well here, but setting
> max_writeback_mb to 128 seems much too large for normal desktop machines.
>
> Because it is so large the background writes don't stop when they get
> down to the background threshold, but just keep on writing.
> background_threshold on my machine is only about 300Mb so it can
> undershoot by quite a bit. This could impact random write workloads
> significantly.
If that's true, would it be even worse for embedded devices with, say,
just 32MB RAM? It sounds like writeback undershoot might be rather
extreme in that case.
Also on this topic, should max_writeback be smaller for slow disks? I
have a small device here with a hard disk that can only be written at
2-10MB/s due to limitations of the built-in IDE controller.
I know that's unusual, but it shows there is quite a wide range of
speeds at which disks can be written, even just counting hard disks.
-- Jamie
--
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