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

[Xen-devel] Re: [Qemu-devel] [PATCH] xen-mapcache: Fix rlimit set size.

To: Alexander Graf <agraf@xxxxxxx>
Subject: [Xen-devel] Re: [Qemu-devel] [PATCH] xen-mapcache: Fix rlimit set size.
From: Anthony PERARD <anthony.perard@xxxxxxxxxx>
Date: Thu, 4 Aug 2011 14:33:44 +0100
Cc: Anthony PERARD <anthony.perard@xxxxxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, QEMU-devel <qemu-devel@xxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Delivery-date: Thu, 04 Aug 2011 06:35:00 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=CrneoUnn+mJyEXz5JBCfPx3JwQXp6xWdKpVD8gSt/dI=; b=BytQjR7XyTL5c4gflLhZgOuKOnaUvgLL0YhYjJdC9w69cC8k6Nf3U7gJYgSjnNVDLD 8aTMWJCTCDJLkpjkN4YYdvWmrGfFlOdQaASP8kJmhr6o9WhOiX4bFElWy6M7o0zrUBXl +AgXvwjEo+oafUHA/sZMlOEUsFQkwBVK2m/dE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E380EB6.6050505@xxxxxxx>
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: <1312226782-26882-2-git-send-email-anthony.perard@xxxxxxxxxx> <4E380EB6.6050505@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, Aug 2, 2011 at 15:50, Alexander Graf <agraf@xxxxxxx> wrote:
> On 08/01/2011 09:26 PM, Anthony PERARD wrote:
>>
>> Previously, the address space soft limit was set mcache_max_size. So,
>> before the mcache_max_size was reached by the mapcache, QEMU was killed
>> for overuse of the virtual address space.
>>
>> This patch fix that by setting the soft limit to mcache_max_size + 80MB.
>> I observed that QEMU use 75MB more than max_mcache_size after several
>> empirical tests.
>
> Not sure I understand. What are those 75MB?

I did the calculation like that:
 - I make sure that the MapCache was full.
 - I did the difference between the value in mapcache->max_mcache_size
and the size of the used address space by the QEMU process.

-- 
Anthony PERARD

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