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] /proc/xen/xenbus supports watch?

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] /proc/xen/xenbus supports watch?
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sun, 25 Sep 2005 12:33:33 +0100
Cc: Rusty Russell <rusty@xxxxxxxxxxxxxxx>, xen-devel List <xen-devel@xxxxxxxxxxxxxxxxxxx>, Christian Limpach <Christian.Limpach@xxxxxxxxxxxx>
Delivery-date: Sun, 25 Sep 2005 11:26:25 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <39daa0554066842da8701a90d9f01386@xxxxxxxxxxxx>
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: <5d7aca9505090801025f3d5771@xxxxxxxxxxxxxx> <3d8eece205090803381b818f18@xxxxxxxxxxxxxx> <1126226609.25110.3.camel@xxxxxxxxxxxxxxxxxxxxx> <3d8eece205091302422ac74f77@xxxxxxxxxxxxxx> <1126657264.7896.20.camel@xxxxxxxxxxxxxxxxxxxxx> <1126689530.4415.10.camel@xxxxxxxxxxxxxxxxxxxxx> <3d8eece205091405555a2871fc@xxxxxxxxxxxxxx> <1126748390.12119.33.camel@xxxxxxxxxxxxxxxxxxxxx> <aad156145bec3bd706ef69c0e96341a7@xxxxxxxxxxxx> <1126945564.29203.116.camel@xxxxxxxxxxxxxxxxxxxxx> <bf4f0a8e8b96fd1ac2701daa78ca52c6@xxxxxxxxxxxx> <1127088661.23870.47.camel@xxxxxxxxxxxxxxxxxxxxx> <d7335251fd831e43f944d94e22da3878@xxxxxxxxxxxx> <1127214064.2656.45.camel@xxxxxxxxxxxxxxxxxxxxx> <152436486e4a36af94a87ad6d40a768e@xxxxxxxxxxxx> <1127354853.7567.6.camel@xxxxxxxxxxxxxxxxxxxxx> <b5423e9d922e98b290db80ff4d0cba9c@xxxxxxxxxxxx> <1127429689.2722.2.camel@xxxxxxxxxxxxxxxxxxxxx> <785f15905bfe17d87d6bd0eb878cc166@xxxxxxxxxxxx> <1127618982.796.71.camel@xxxxxxxxxxxxxxxxxxxxx> <39daa0554066842da8701a90d9f01386@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 25 Sep 2005, at 12:02, Keir Fraser wrote:

Yeah, I can live with this, although: What about multiple transactions within the kernel? Do you plan to continue serialising them (e.g., on a waitqueue)? An advantage of mux/demux would be that concurrent kernel transactions could easily use the same mechanism. Your scheme places restart mechanisms in user space, so they're out of reach for kernel transactions.

Also, page-per-connection won't entirely avoid sharing of state/resource in xenstored. At some point we'll want to add per-domain access policy, and space/bandwidth quotas (to prevent DoS). All of those must be shared between the multiple connections of a domain -- so the separate connections aren't as independent as you might like.

 -- Keir


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