[Top] [All Lists]

Re: 12x performance drop on md/linux+sw raid1 due to barriers [xfs]

To: "Peter Grandi" <pg_mh@xxxxxxxxxx>, "Linux RAID" <linux-raid@xxxxxxxxxxxxxxx>, "Linux XFS" <xfs@xxxxxxxxxxx>
Subject: Re: 12x performance drop on md/linux+sw raid1 due to barriers [xfs]
From: "Leon Woestenberg" <leonw@xxxxxxxxxxx>
Date: Mon, 22 Dec 2008 14:19:02 +0100
In-reply-to: <18766.38416.161254.375311@xxxxxxxxxxxxxxxxxx>
References: <alpine.DEB.1.10.0812060928030.14215@xxxxxxxxxxxxxxxx> <1229225480.16555.152.camel@localhost> <18757.4606.966139.10342@xxxxxxxxxxxxxxxxxx> <200812141912.59649.Martin@xxxxxxxxxxxx> <18757.33373.744917.457587@xxxxxxxxxxxxxxxxxx> <494971B2.1000103@xxxxxxx> <494A07BA.1080008@xxxxxxxxxxx> <18766.38416.161254.375311@xxxxxxxxxxxxxxxxxx>

On Sun, 21 Dec 2008 19:16:32 +0000, "Peter Grandi" <pg_mh@xxxxxxxxxx>
> > The drive itself may still re-order writes, thus can cause
> > corruption if halfway the power goes down. [ ... ] Barriers need
> > to travel all the way down to the point where-after everything
> > remains in-order. [ ... ] Whether the data has made it to the
> > drive platters is not really important from a barrier point of
> > view, however, iff part of the data made it to the platters, then
> > we want to be sure it was in-order. [ ... ]
> But this discussion is backwards, as usual: the *purpose* of any
> kind of barriers cannot be just to guarantee consistency, but also
> stability, because ordered commits are not that useful without
> commit to stable storage.
I do not see in what sense you mean "stability"? Stable as in BIBO or

Barriers are time-related. Once data is on storage, there is no relation
with time.

So I do not see how barriers help to "stabilize" storage.

Ordered commits is a strong-enough condition to ensure consistency in
the sense that
atomic transactions either made it to the disk completely or not at all.

> If barriers guarantee transaction stability, then consistency is
> also a consequence of serial dependencies among transactions (and
> as to that per-device barriers are a coarse and very underoptimal
> design).
Of course, the higher level should ensure that between transactions, the
(meta)data is always consistent.

In filesystem design, we see that some FS's decide to split metadata and
data in this regard.

> Anyhow, barriers for ordering only have been astutely patented
> quite recently:
> http://www.freshpatents.com/Transforming-flush-queue-command-to-memory-barrier-command-in-disk-drive-dt20070719ptan20070168626.php
> Amazing new from the patent office.y
Grand. Another case of no prior art. :-)


<Prev in Thread] Current Thread [Next in Thread>