[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AA26055.2090400@rtr.ca>
Date: Sat, 05 Sep 2009 08:57:57 -0400
From: Mark Lord <lkml@....ca>
To: Ric Wheeler <rwheeler@...hat.com>
Cc: Krzysztof Halasa <khc@...waw.pl>,
Christoph Hellwig <hch@...radead.org>,
Michael Tokarev <mjt@....msk.ru>, david@...g.hm,
Pavel Machek <pavel@....cz>, Theodore Tso <tytso@....edu>,
NeilBrown <neilb@...e.de>, Rob Landley <rob@...dley.net>,
Florian Weimer <fweimer@....de>,
Goswin von Brederlow <goswin-v-b@....de>,
kernel list <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...l.org>, mtk.manpages@...il.com,
rdunlap@...otime.net, linux-doc@...r.kernel.org,
linux-ext4@...r.kernel.org, corbet@....net
Subject: Re: wishful thinking about atomic, multi-sector or full MD stripe
width, writes in storage
Ric Wheeler wrote:
> On 09/04/2009 05:21 PM, Mark Lord wrote:
..
>> How about instead, *fixing* the MD layer to properly support barriers?
>> That would be far more useful, productive, and better for end-users.
..
> Fixing MD would be great - not sure that it would end up still faster
> (look at md1 devices with working barriers with compared to md1 with
> write cache disabled).
..
There's no inherent reason for it to be slower, except possibly
drives with b0rked FUA support.
So the first step is to fix MD to pass barriers to the LLDs
for most/all RAID types.
Then, if it has performance issues, those can be addressed
by more application of little grey cells. :)
Cheers
--
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