From: Thanos Makatos <thanos.makatos@citrix.com>
To: xen-devel@lists.xensource.com
Cc: thanos.makatos@citrix.com
Subject: [PATCH 0 of 5 RFC] blktap3: Introduce xenio daemon (coordinate blkfront with tapdisk).
Date: Wed, 28 Nov 2012 14:20:10 +0000 [thread overview]
Message-ID: <patchbomb.1354112410@makatos-desktop> (raw)
This patch series introduces the xenio daemon. 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.
This series requires the RFC series described in
http://lists.xen.org/archives/html/xen-devel/2012-11/msg00875.html
in order to compile.
next reply other threads:[~2012-11-28 14:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 14:20 Thanos Makatos [this message]
2012-11-28 14:20 ` [PATCH 1 of 5 RFC] blktap3: Introduce fundamental xenio headers Thanos Makatos
2012-11-29 15:14 ` Ian Campbell
2012-12-03 18:04 ` Thanos Makatos
2012-11-28 14:20 ` [PATCH 2 of 5 RFC] blktap3: Logging for the xenio daemon and libxenio Thanos Makatos
2012-11-29 15:15 ` Ian Campbell
2012-11-28 14:20 ` [PATCH 3 of 5 RFC] blktap3: Introduce xenio.c, core xenio daemon functionality Thanos Makatos
2012-11-29 15:26 ` Ian Campbell
2012-12-04 10:01 ` Thanos Makatos
2012-11-28 14:20 ` [PATCH 4 of 5 RFC] blktap3: Introduce xenio daemon Makefile Thanos Makatos
2012-11-29 15:32 ` Ian Campbell
2012-12-04 11:53 ` Thanos Makatos
2012-12-04 11:59 ` Ian Campbell
2012-11-28 14:20 ` [PATCH 5 of 5 RFC] blktap3: Add the xenio binaries to the Mercurial ignore list Thanos Makatos
2012-11-29 15:12 ` [PATCH 0 of 5 RFC] blktap3: Introduce xenio daemon (coordinate blkfront with tapdisk) Ian Campbell
2012-12-03 17:55 ` Thanos Makatos
2012-12-04 9:24 ` Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=patchbomb.1354112410@makatos-desktop \
--to=thanos.makatos@citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).