Mr. Hellwig,
I usually like to start with an interface and then implement the driver's from there.
In this case, this is a block-level interface that supports new functionality (atomic writes). In the past, you would approach this type of problem by having the atomic and user layers as a monolithic solution. Consider database updates and the complexity that they go through to insure database integrity. If a block device could provide a database with an atomic update interface, the database would get a lot simpler. The same discussion holds true for file systems. Depending on the atomic update implementation, you might end up in the same place in terms of total code, but you might also end up somewhere completely different.
The impetus for this is some research on file system "write amplification". In general, file system design seems to be heading in the direction of higher and higher write amplification. For example, the tree structure of zfs is shockingly inefficient in terms of write overhead. This is happening at the same time as Flash is becoming popular but is also moving to smaller and smaller geometries. So write efficiency is becoming more and more important.
By decoupling the atomic update semantics from file system and other block device "users", this gives devices the opportunity to implement atomic updates internal to or in cooperation with Flash management algorithms. In theory, you can implement atomic updates without any extra writes. In practice, some devices will be better than others.
I was hoping to stumble across someone interested in this as a concept, or someone who has researched this area, as I don't have any near production existing code. I could pretty easily hack in a couple of extra fields in struct bio that would accomplish what I see, but others might have differing input.
Doug Dumitru
On Wed, Jul 8, 2015 at 12:38 PM, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote:
On Wed, Jul 08, 2015 at 09:21:21AM -0700, Doug Dumitru wrote:
> I have a "smart" block device that can implement multi-segment atomic
> writes.
How about submitting your driver upstream first and then we can work
with you on an API that fits the devices and the consumers needs.
--
Doug Dumitru
EasyCo LLC
EasyCo LLC
-- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
