Re: [Xen-devel] [PATCH 2 of 3] blktap3/libxl: Check whether blktap3 is available

[Thanos Makatos <thanos.makatos@xxxxxxxxxx>]

> So if all you're doing is seeing whether it's available, surely you can
> have it write something in a fixed location in xenstore on startup ?
> 
> > However, the control socket will be necessary for doing more
> elaborate
> > stuff (e.g. controlling a tapdisk in a thread-safe manner).
> 
> I'm not sure I understand this comment.  What is not thread-safe about
> controlling it via xenstore ?

There are some operations that need to be performed on running tapdisks that do 
not involve XenStore, e.g. refreshing a tapdisk as the result of a VHD snapshot 
operation.

> 
> > I understand the problems of using a processes' name in this case,
> but
> > since the control socket is not absolutely necessary at this point
> > (it's actually not yet implemented in the tapback daemon), could we
> > leave this as a future improvement?
> 
> On the whole I think it would be better not to introduce bugs on the
> vague promise of fixing them later "as a future improvement" ...

Fair enough!

> 
> Thanks,
> Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel