From: Thanos Makatos <thanos.makatos@citrix.com>
To: xen-devel@lists.xensource.com
Cc: thanos.makatos@citrix.com
Subject: [PATCH 0 of 7 v2] blktap3: Introduce the tapback daemon (most of blkback in user-space).
Date: Fri, 4 Jan 2013 12:14:00 +0000 [thread overview]
Message-ID: <patchbomb.1357301640@makatos-desktop> (raw)
This patch series introduces the tapback daemon, the user space daemon that
acts as a device's back-end, essentially most of blkback in user space. The
daemon is responsible for coordinating the front-end and tapdisk. It instructs
the tapdisk to connect to/disconnect from the shared ring, and manages the
state of the back-end.
The shared ring between the front-end and tapdisk is created by a library that
will be introduced in another patch series (the entry point is function
tap_ctl_connect_xenblkif in frontend.c). This library also contains the
functionality that enables tapdisk to directly access the shared ring.
This series requires the RFC series described in
http://lists.xen.org/archives/html/xen-devel/2012-12/msg00254.html
in order to compile.
---
Changes since v1:
The series has been largely reorganised:
* Renamed the daemon from xenio to tapback.
* Improved description in patch 0.
* Merged structures and functions.
* Disaggregated functionality from the core daemon source file to smaller ones
in order to facilitate the review process and improve maintenance.
next reply other threads:[~2013-01-04 12:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 12:14 Thanos Makatos [this message]
2013-01-04 12:14 ` [PATCH 1 of 7 v2] blktap3/tapback: Introduce core defines and structure definitions Thanos Makatos
2013-01-18 15:28 ` Ian Campbell
2013-01-25 13:25 ` Thanos Makatos
2013-01-04 12:14 ` [PATCH 2 of 7 v2] blktap3/tapback: Introduces functionality required to access XenStore Thanos Makatos
2013-01-18 16:08 ` Ian Campbell
2013-01-25 14:03 ` Thanos Makatos
2013-01-25 14:13 ` Ian Campbell
2013-01-04 12:14 ` [PATCH 3 of 7 v2] blktap3/tapback: Logging for the tapback daemon and libxenio Thanos Makatos
2013-01-04 12:14 ` [PATCH 4 of 7 v2] blktap3/tapback: Introduce back-end XenStore path handler Thanos Makatos
2013-01-18 17:07 ` Ian Campbell
2013-01-25 14:31 ` Thanos Makatos
2013-01-25 14:38 ` Ian Campbell
2013-01-04 12:14 ` [PATCH 5 of 7 v2] blktap3/tapback: Introduce front-end " Thanos Makatos
2013-01-18 17:17 ` Ian Campbell
2013-01-25 15:09 ` Thanos Makatos
2013-01-25 16:15 ` Ian Campbell
2013-01-04 12:14 ` [PATCH 6 of 7 v2] blktap3/tapback: Introduce the tapback daemon Thanos Makatos
2013-01-04 12:14 ` [PATCH 7 of 7 v2] blktap3/tapback: Introduce tapback daemon Makefile Thanos Makatos
2013-01-18 17:21 ` 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.1357301640@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).