WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] blktap2: add blktap2 device class anddevicecontr

To: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] blktap2: add blktap2 device class anddevicecontroller
From: Ryan O'Connor <rjo@xxxxxxxxx>
Date: Tue, 30 Jun 2009 23:04:18 -0700
Cc: dmeyer@xxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, keir.fraser@xxxxxxxxxxxxx
Delivery-date: Tue, 30 Jun 2009 23:07:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C2C9FA0F0FA8B3kanno.masaki@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <6295171d4ccc60f80f04.1246409384@xxxxxxxxxxxxxxxxxxxxxxxx> <C1C9FA05191C6Dkanno.masaki@xxxxxxxxxxxxxx> <C2C9FA0F0FA8B3kanno.masaki@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
Hi Kan,

On Wed, Jul 01, 2009 at 02:44:55PM +0900, Masaki Kanno wrote:
> Hi Ryan,
> 
> I thought... 
> Are blktap1 and blktap2 used as follows? 
> And the head of the string of disk parameters for blktap devices is 
> 'tap:' only, isn't it?
> Is my understanding right?
> 
>      |        blktap2        |
>      +-----------+-----------+
>      | Installed | Not       |
>      |           | Installed |
> -----+-----------+-----------+
> aio  |blktap2    |blktap1    |
> -----+-----------+-----------+
> sync |blktap1    |blktap1    |
> -----+-----------+-----------+
> vmdk |blktap1    |blktap1    |
> -----+-----------+-----------+
> ram  |blktap2    |blktap1    |
> -----+-----------+-----------+
> qcow |blktap2    |blktap1    |
> -----+-----------+-----------+
> qcow2|blktap1    |blktap1    |
> -----+-----------+-----------+
> vhd  |blktap2    |blktap1    |
> -----+-----------+-----------+
> ioemu|blktap1    |blktap1    |
> -----+-----------+-----------+

Yes, you are correct. Also, note that this is the same way
BlktapController created blktap1 and blktap2 devices before my patch.

> Wed, 01 Jul 2009 13:33:35 +0900, Masaki Kanno wrote:
> 
> >Hi Ryan,
> >
> >>blktap2 devices must be handled differently than blktap2 devices. blktap2
> >                                                  ^^^^^^^
> >                                                  blktap1?  typo?

Thanks, this is a typo. It should say "blktap1".

Thanks again
Ryan
--
  Ryan O'Connor <rjo@xxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel