Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

[Xen-devel] Re: [PATCH] have udev create the device for blktap

To: "Steven Rostedt" <srostedt@xxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH] have udev create the device for blktap
From: "Andrew Warfield" <andrew.warfield@xxxxxxxxxxxx>
Date: Thu, 28 Sep 2006 14:04:36 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 28 Sep 2006 17:47:31 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=GSCKNbrzYvc2HWQUwYc0ofmsIm0Fl1rwKxUIW68ptxFRblHmc/wnycuVW8Km0TKfuz4KMo1pZHYyqAMYCeAzt6AKUO5hPtBrn+ncOlBmmud6MjDDXjeghGuscdfplGxvuPAZFD7hAyn9dsodJqdmoZ/S46nlAZSTO8K//XSJg68=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <451C37CB.4070201@xxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <451BD64B.4040500@xxxxxxxxxx> <eacc82a40609281323h5c2d37e8n13750116fcf03432@xxxxxxxxxxxxxx> <451C37CB.4070201@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Ships in the night, and so on -- as I posted concurrently with this, I
applied the patch. ;)

Anyhow, thanks for the clarifications, and I agree with your points
about evntchn moving to a dynamic minor and the tap interrogation
moving from /proc/devices to /sys -- that would all be great.

> Also, on the blocktap side, it would be nice (in a later patch) to
> kill the static allocation of the data-path devices and allocate them
> on demand, as you do with the associed sysfs entries.

That would not be a problem.  The tap devices could be stored in a link
list. The only time you would need to search the list to find the tap
device, is really on open.  You would also do it to look for a free
device, but that search is already done.

I'll take a look into that too.

Perfect -- this would be a very welcome patch.

Thanks again!
a.

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

<Prev in Thread] Current Thread [Next in Thread>