From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Thanos Makatos <thanos.makatos@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: RFC: blktap3
Date: Mon, 13 Aug 2012 10:25:11 -0400 [thread overview]
Message-ID: <20120813142511.GD14666@phenom.dumpdata.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1208101216490.21096@kaball.uk.xensource.com>
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
:-)
next prev parent reply other threads:[~2012-08-13 14:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 14:03 RFC: blktap3 Thanos Makatos
2012-08-09 16:04 ` Ian Campbell
2012-08-09 18:04 ` Konrad Rzeszutek Wilk
2012-08-09 19:05 ` Ian Campbell
2012-08-10 11:02 ` Thanos Makatos
2012-08-10 11:17 ` Stefano Stabellini
2012-08-13 14:25 ` Konrad Rzeszutek Wilk [this message]
2012-08-09 21:39 ` Goncalo Gomes
2012-08-10 11:06 ` Thanos Makatos
2012-08-10 13:11 ` Jan Beulich
2012-08-10 13:25 ` Thanos Makatos
2012-08-10 11:30 ` Thanos Makatos
2012-08-16 16:09 ` Ian Campbell
2012-08-30 15:41 ` Thanos Makatos
2012-08-30 15:46 ` 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=20120813142511.GD14666@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=thanos.makatos@citrix.com \
--cc=xen-devel@lists.xen.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.