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

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

> > 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.
> You mean "there are some operations whose control path will be outside
> xenstore in the current design", I think ?


> How will these control operations be invoked when the tapdisk is
> running in a driver/stub/backend domain rather than the same domain as
> the main toolstack ?

I haven't given much thought to that, but I believe there are a number of 
viable options. We could use XenStore, though I think we should avoid doing 
that for performance reasons. I assume the tapdisk(s) will be running on the 
same domain the tapback daemon is, so we can make tapback listen on a socket in 
order that the toolstack running on another domain can talk to it. Does this 
sound plausible?

> Ian.

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.