Neil, Neil Brown wrote: > Maybe if you explain more about what would be the specifics of these > ioctls that you want to pass down. Sure, no problem... > > asynchronous replication - to get acceptable performance when the backup > > leg of the raid1 mirror is slow (e.g., nbd over a LAN or WAN) > > Hmmm. I cannot figure out exactly what would be asynchronous... Nor > can I see how this would require an ioctl. Basically, we're trying to overcome latency penalties associated with writing data and waiting for acknowledgements over a network (or any other slow transport). So, all writes to the backup device(s) would be queued, so that the writes could take place asynchronously. The size of the queue and whether or not to enable this asynchronous mode would be user-configurable; that's where the ioctls come in. Since user configuration of the md driver is currently done with ioctls, this seemed like the natural choice. Of course, I'm open to other suggestions, if there's a better way to do this... -- Paul - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
