From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thanos Makatos 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 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xensource.com Cc: thanos.makatos@citrix.com List-Id: xen-devel@lists.xenproject.org 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.