Re: Device loses barrier support (was: Fixed patch for simple barriers.)

From: Andi Kleen
Date: Thu Dec 04 2008 - 21:58:38 EST

> The only one offender is "md".

I'm not sure. It wouldn't surprise me if it can happen with other setups
too. Perhaps Chris knows more.

> It is less overhead to change "md" to play
> nice and be reliable than to double-submit requests in all the places that
> needs write ordering.

They do that already anyways.

> > > * the filesystems developed hacks to work around this issue, the hacks
> > > involve not submitting more requests after the barrier request,
> >
> > I suspect the reason the file systems did it this way is that
> > it was a much simpler change than to rewrite the transaction
> > manager for this.
> It could be initial reason. But this unreliability also disallows any
> improvement in filesystems. No one can write asynchronous transaction
> manager because of that evil EOPNOTSUPP.

Doesn't seem right. It would be a simple state machine
to handle it fully asynchronous. Alternatively you could
always use empty barriers.

But we can worry about that when some in tree file system
actually tries to do that.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at