From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: RFC: blktap3 Date: Mon, 13 Aug 2012 10:25:11 -0400 Message-ID: <20120813142511.GD14666@phenom.dumpdata.com> References: <4B45B535F7F6BE4CB1C044ED5115CDDE0107F6C1D44C@LONPMAILBOX01.citrite.net> <20120809180433.GA14457@phenom.dumpdata.com> <4B45B535F7F6BE4CB1C044ED5115CDDE0107F6C1D55E@LONPMAILBOX01.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefano Stabellini Cc: Thanos Makatos , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On Fri, Aug 10, 2012 at 12:17:10PM +0100, Stefano Stabellini wrote: > On Fri, 10 Aug 2012, Thanos Makatos wrote: > > Hi Konrad, > > > > I'm not sure I understand your question. Blktap3 lives in tools/blktap3. The component that allows tapdisk3 to talk directly to blkfront is xenio, it lives in blktap3/tools/xenio. Since tapdisk3 can talk to blkfront via xenio, it doesn't interact with blkback/blktap kernel drivers. > > Konrad, Blktap3 is purely userspace ;-) I somehow managed to miss the blktap3.bz2 file in the original thread and then started looking for a git tree or hg tree and couldn't find it. So the answer to my question is: http://lists.xen.org/archives/html/xen-devel/2012-08/binRhvyhiESWY.bin :-)