On 1/10/18 12:26 PM, Mike Christie wrote: > On 01/04/2018 10:11 AM, Bryant G. Ly wrote: >> This patch allows for multiple attributes to be reconfigured >> and handled all in one call as compared to multiple netlinks. >> >> Example: >> set attribute dev_reconfig=dev_config=fbo//home/path:dev_size=2147483648 >> > I know I suggested this, but I think I was wrong. If we have to support > other apps that work in reverse to targetcli+tcmu-runner where the > tcmu-runner equivalent app sets things up then contacts the kernel, > let's just not do passthrough operations like this for reconfig. There > is no need to bring in the kernel. > > For the initial config we can still do it since we have to maintain > compat, but for major reconfigs like this let's just have targetcli > contact tcmu-runner, then runner can update the kernel if needed. > > So in targetcli and runner copy the check_config stuff, and add a > reconfig callout that works like it. We then do not have this weird > kernel passthrough and do not have to worry about the non > targetcl-tcmu-runner type of model. > > > So you basically want me to use DBUS correct? Connect a GCallback function with reconfig function and use DBUS to pass info back to kernel if necessary? -Bryant
