On 07/28/2010 11:00 AM, Christoph Hellwig wrote: > On Wed, Jul 28, 2010 at 10:58:30AM +0200, Tejun Heo wrote: >> I see. It probably would be good to have ordering requirements >> carried in the bio / request, so that filesystems can mix and match >> barriers of different strengths as necesasry. As you seem to be >> already working on it, are you interested in pursuing that direction? > > I've been working on that for a while, but it got a lot more urgent > as there's been an application hit particularly hard by the barrier > semantics on cache less devices and people started getting angry > about it. That's why fixing this for cache less devices has become > a higher priority than solving the big picture. Well, if disabling barrier works around the problem for them (which is basically what was suggeseted in the first message), that's not too bad for short term, I think. At least, there's a handy workaround. I'll re-read barrier code and see how hard it would be to implement a proper solution. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
