> In more detail: ddlink is a generic pipe-like interface for controlling
> device drivers.
I'm not in a position to say much about the wider picture at the moment,
but one quibble comes immediately to mind: why do you create yet another
communication path into the kernel rather than using netlink, which is
already there and used in a number of other contexts?
dm-devel mailing list