Re: TCMU and libtcmu.so

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Andy, let me clarify my position on DBus. The following components are easily installed on the latest Debian/Ubuntu system: dbus, libdbus, libdbus-glib as well as libnl 3. Their presence is not a problem in my environment.

The run-time configuration is another matter as I would like to run user-mode LIO backends inside containers. This means limiting/removing the system interactions as much as possible. Ideally, the backend would implement both device discovery/configuration as well as data processing. This gives me the freedom to implement the event loop(s) and handle I/O from a device(s) in whatever way I see fit. The user-mode process would only rely on the kernel facilities (well, as well as the packaged shared libs) and the TCMU plugin configuration would be fixed.

How about a compromise - DBus API is always available, yet only used when it is meaningful. That is when the handlers are loaded on the fly into tcmu-runner. I.e. there would static and dynamic ways to configure handlers and devices.

Oleg.


On 2015-11-24 14:08, Andy Grover wrote:
Hi Oleg and everyone,

I've been working on moving TCMU handling into a library so existing apps can integrate TCMU processing into their event loops.

In the case where you *don't* need to run the event loop, the existing support for tcmu-runner handler plugins is unchanged.

https://github.com/agrover/tcmu-runner/pull/16

One remaining TBD is the work to enable tcmu-runner/libtcmu to enable unified discovery of available handlers. This is partly because I haven't gotten to it yet :) but also because Oleg expressed a reluctance to accept a dependency on a DBus library, which is needed for unified discovery.

Maybe a move to sd-bus instead of GDBus would make it more palatable? In any case, I think we need to have that discussion before it makes sense to work on unified discovery.

Thoughts?

Regards -- 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



[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux