From: Paolo Bonzini <pbonzini@redhat.com>
To: Zhanghailiang <zhang.zhanghailiang@huawei.com>,
"quintela@redhat.com" <quintela@redhat.com>,
"edgar.iglesias@xilinx.com" <edgar.iglesias@xilinx.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
"kwolf@redhat.com" <kwolf@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"libvir-list@redhat.com" <libvir-list@redhat.com>
Cc: Zhouxiangjiu <zhouxiangjiu@huawei.com>,
Huazhiqiang <huazhiqiang@huawei.com>,
Huangzhichao <huangzhichao@huawei.com>,
"Huangpeng (Peter)" <peter.huangpeng@huawei.com>
Subject: Re: [Qemu-devel] [RFC] support memory reserved feature and optimize mlock guest memory propose
Date: Wed, 05 Mar 2014 09:56:35 +0100 [thread overview]
Message-ID: <5316E6C3.3030502@redhat.com> (raw)
In-Reply-To: <D1BD20B5DB34024DA951CEEE6C4C599859618ED9@szxema505-mbs.china.huawei.com>
Il 05/03/2014 09:01, Zhanghailiang ha scritto:
> Hi all：
>
> Currently, we use cgroup(memory) to support memory QoS on KVM platform,
> and use "mlock" on qemu to support "memory reserved".
>
> The "mlock" seems to be not appropriate.
>
> Now qemu "mlock" memory in the main thread, which would lock iothread
> (qemu_mutex_lock_iothread), if the memory size is large, that will
> consume lots of time.
>
> It means whenever we want to set a new 'mlock', the VM would be blocked
> for a while.
I'm not sure I understand how the mlock-ed memory is used. Are you
using a custom malloc, for example with g_mem_set_vtable?
Paolo
next prev parent reply other threads:[~2014-03-05 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 8:01 [Qemu-devel] [RFC] support memory reserved feature and optimize mlock guest memory propose Zhanghailiang
2014-03-05 8:56 ` Paolo Bonzini [this message]
2014-03-06 8:06 ` Zhanghailiang
2014-03-06 8:41 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5316E6C3.3030502@redhat.com \
--to=pbonzini@redhat.com \
--cc=edgar.iglesias@xilinx.com \
--cc=huangzhichao@huawei.com \
--cc=huazhiqiang@huawei.com \
--cc=kwolf@redhat.com \
--cc=libvir-list@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@gmail.com \
--cc=zhang.zhanghailiang@huawei.com \
--cc=zhouxiangjiu@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.