Re: [Xen-devel] [PATCH 0 of 5 RFC] blktap3: Introduce xenio daemon (coordinate blkfront with tapdisk).

[Thanos Makatos <thanos.makatos@xxxxxxxxxx>]

> On Wed, 2012-11-28 at 14:20 +0000, Thanos Makatos wrote:
> > This patch series introduces the xenio daemon.
> 
> Can we call it something less generic?

Sure, though I don't really have good alternatives. Conceptually this daemon is 
blkback's user space counterpart, but naming it blkback would bring much 
confusion I believe. What about "tapback"? (Just a suggestion.)

> 
> >  This daemon is responsible for
> > coordinating blkfront and tapdisk, when blkfront changes state. It
> does so by
> > monitoring XenStore for blkfront state changes. The daemon
> creates/destroys the
> > shared ring, instructs the tapdisk to connect to/disconnect from it,
> and
> > manages the state of the back-end.
> 
> So xenio creates the ring and manages xenstore? How does tapdisk get
> access to the ring?

Exactly, xenio creates the ring and manages xenstore. Tapdisk accesses the 
shared ring via a static library that will be introduced by another patch 
series -- it's the series I'm currently working on. I'll update this series' 
description to clarify this.

> 
> >
> > This series requires the RFC series described in
> > http://lists.xen.org/archives/html/xen-devel/2012-11/msg00875.html
> > in order to compile.
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxx
> > http://lists.xen.org/xen-devel
> 

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