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/
Home Products Support Community News


Re: [Xen-devel] xenstored misaccounting resource limits

To: Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] xenstored misaccounting resource limits
From: John Levon <levon@xxxxxxxxxxxxxxxxx>
Date: Wed, 23 May 2007 14:01:43 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, max.zhen@xxxxxxx
Delivery-date: Wed, 23 May 2007 05:54:48 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C279B7FB.F60D%keir@xxxxxxxxxxxxx>
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: <20070523024610.GA16190@xxxxxxxxxxxxxxxxxxxxxxx> <C279B7FB.F60D%keir@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Wed, May 23, 2007 at 09:20:59AM +0100, Keir Fraser wrote:

> > Currently xenstored does not account domain->nbentry when a transaction
> > is aborted (either intentionally or via EAGAIN). We hit this case when
> > adding a lot of disks to a domU: the limit is reached much earlier than
> > expected, as a number of clashing transactions cause incorrect inflation
> > of the value of ->nbentry.
> > 
> > There's been a little discussion internally on the nicest way to fix
> > this. My current suggestion is along the lines of:
> The principle is clearly right, but domain_nbcount[] isn't a great idea

That was shorthand, we'd keep a list.


Xen-devel mailing list

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