> Well, I can definitely understand your reservations about the code; it's > strange and foreign and complicated. But having beaten my head against > the various problems and difficulties inherent in asynchronous > programming for years - well, having found a way to make it sane to me > it'd be madness to go back. I think its more of a different paradigm than complicated. The big question I'd have to ask is how does it fit with hard real time. That is a big issue given the gradual merging and getting of "hard" real time into the kernel proper. In some ways it's not that strange either. A look at what happens on some of our kref handling in drivers is very similar but hardcoded. Is the handling of priority inversion within closures a well understood and solved problem ? Alan -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
