FW: (no subject)

From: "Izik Eidus" <izik.eidus-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: FW:  (no subject)
Date: Sun, 12 Aug 2007 15:43:28 -0700	[thread overview]
Message-ID: <64F9B87B6B770947A9F8391472E032160CBECF4B@ehost011-8.exch011.intermedia.net> (raw)
In-Reply-To: 64F9B87B6B770947A9F8391472E032160CBECF4A@ehost011-8.exch011.intermedia.net

[-- Attachment #1.1: Type: text/plain, Size: 2420 bytes --]

-----הודעה מקורית-----
מאת: Izik Eidus
נשלח: א 12/08/2007 15:43
אל: Anthony Liguori
נושא: RE: [kvm-devel] (no subject)

hey Anthony,
yes i think you are right.
passing a pointer sound smarter to me.
i dont think we should care at all about the kvmctl API, and as you said
in this way it would be possible to do the memory allocation at QEMU.

(this evil whitespaces ...)

thanks.

-----הודעה מקורית-----
מאת: Anthony Liguori [mailto:anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org]
נשלח: א 12/08/2007 14:37
אל: Izik Eidus
עותק לידיעה: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
נושא: Re: [kvm-devel] (no subject)

Hi Izik,

On Sun, 2007-08-12 at 12:59 -0700, Izik Eidus wrote:
> we are working on swapping support for the guests in kvm.
> we want to allow management of the memory swapping of the guests from
> kvm.
> 
> i wrote this patch that move the guest allocated memory from the
> kernel to the userspace for better management.
> plus in this way it will share more code for such soultion with s390
> and other archs.

Do we care much about maintaining the kvmctl API?  I ask because I think
it would be nice to provide a pointer to kvmctl instead of having it
allocate the memory.  I think there are a few advantages to this.

It simplifies the QEMU patch and it allows for the logic for choosing
how memory is allocated to be done in QEMU.  I'm thinking about things
like allocating memory from hugetlbfs.  Since large pages are a sparse
commodity, I don't think we want to use large pages unless the user asks
us to.  Seems like this logic is best suited to be in QEMU to me.

Otherwise, this page seems pretty good to me.

There's some whitespace damage in this patch to btw.

Regards,

Anthony Liguori

> this is request for comment, so any idea you have please write to me.
> 
> thanks
> 
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________ kvm-devel mailing list kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org https://lists.sourceforge.net/lists/listinfo/kvm-devel

[-- Attachment #1.2: Type: text/html, Size: 3350 bytes --]

[-- Attachment #2: Type: text/plain, Size: 315 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel