Subject: Re: wd, disk write cache, sync cache, and softdep.
To: Manuel Bouyer <email@example.com>
From: Bill Studenmund <firstname.lastname@example.org>
Date: 12/17/2004 18:03:47
Content-Type: text/plain; charset=us-ascii
On Fri, Dec 17, 2004 at 09:09:23PM +0100, Manuel Bouyer wrote:
> On Fri, Dec 17, 2004 at 01:56:46PM -0600, Eric Haszlakiewicz wrote:
> > How can it know A1 is done if there's no way to tell the drive to
> > flush its cache? A possible timeline I see is:
> > send A1, drive says OK,
> > send A2, drive says OK,
> > send A3+FUA, drive writes A3 (due to FUA), drive says OK,
> > drive writes A2, drive writes A1
> If you issue A3 with an "ordered queue tag", then the FUA on A3 will forc=
> and A2 before A3. But you can still have A2, A1, A3.
I'm starting to feel like a broken record. "Ordered" queue tags won't=20
help, if we're trying to get around the write cache. All the ordered tag=20
does is mean we don't start writing A2 into the cache until we've said A1=
is done, and likewise we don't start writing A3 into the cache until A2 is=
done. With a write-back cache, we still have whatever ordering we want in=
getting data out of the cache.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)
-----END PGP SIGNATURE-----