On 10/14/2015 01:39 PM, Oleg Smolsky wrote:
While I cannot comment on the kernel-mode code, the user-mode part certainly needs love. Today, tcmu-runner owns the worker threads, thus forcing the users' code into the plugin structure. This certainly works for minimal examples, but prevents any kind of embedding into larger 3rd-party applications. Production-grade applications generally have their own threading structure and want to deal with socket/file/tcmu notifications in an async way. As such, I just need a library with add_device(), handle_device_events() and handle_one_command() from main.c and most of api.c to talk to the kernel. Tcmu-runner could use the very same library and maintain the existing threading model. I can contribute the changes if such a structure is agreeable.
This would be most welcome. Thanks! -- Andy -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
