On Wed, 2009-04-08 at 09:37 -0400, Mikulas Patocka wrote: > So there are two ways: > > - either support only what all in-kernel filesystems do. Using barrier > reqiests to flush hw cache. You can remove support for barriers with data, > leave just zero-data barrier, you can remove ordering restrictions. > In-kernel filesystems never overlap barrier with another metadata request > (see above why such overlap can't work), so you can freely reorder > zero-data barriers and simplify the code ... because all the requests that > could be submitted in paralel with the barrier are either for different > partition or non-metadata requests to the same partition from prefetch, > direct io or so. > > - or you can allow barriers to be used for purposes as I did. And then, > there must be clean indicator "this device supports barriers > *and*will*support*them*in*the*future*". Currently there is no such > indicator. I'm afraid expecting barriers forever in the future isn't completely compatible with dm or md. Both of these allow the storage to change over time, and the filesystem needs to handle this without corruptions. -chris -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
