From: Zhong Yang <yang.zhong@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, yang.zhong@intel.com,
anthony.xu@intel.com, stefanha@redhat.com, berrange@redhat.com,
stone.xulei@huawei.com, arei.gonglei@huawei.com,
wangxinxin.wang@huawei.com, weidong.huang@huawei.com,
zhang.zhanghailiang@huawei.com, liujunjie23@huawei.com
Subject: Re: [Qemu-devel] [Question] Qemu's Heap Becomes Very Large and Never Reduce Down
Date: Thu, 16 Nov 2017 09:43:46 +0800 [thread overview]
Message-ID: <20171116014346.GA16015@yangzhon-Virtual> (raw)
In-Reply-To: <d344052d-ac24-2ce0-38bc-b8008c895946@redhat.com>
On Wed, Nov 15, 2017 at 02:18:55PM +0100, Paolo Bonzini wrote:
> On 15/11/2017 04:14, Xulei (Stone) wrote:
> > Hi, guys
> >
> > I met a strange problem, with qemu 2.8.1:
> > qemu consumes too many heap memory after several operations and can not
> > release them anymore:
> > hot pulg/unplug disk & net, vnc connect/disconnect, guestOS reboot, etc.
>
> Try with newer QEMU; until recently we used a lot of memory at startup,
> but it was improved in 2.11.
>
> However, I think Anthony also had a patch adding a malloc_trim call in
> the RCU thread, which improved memory usage. Anthony, do you know if
> this is still necessary in 2.11?
>
Hello Paolo,
Last time, when you traveled in BeiJing, we talked about this malloc_trim()
solution in RH office. At that time, you asked me to send this patch to upstream.
I can try this patch in the newest Qemu version if you regard this solution is
suitable.
I also want to look for other more better solution, but there are some urgency
tasks interrupt me.
In fact, Anthony also have some other solutions for heap memory deduction in
our intel ClearContainer.
Regards,
Yang Zhong
> Thanks,
>
> Paolo
next prev parent reply other threads:[~2017-11-16 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 3:14 [Qemu-devel] [Question] Qemu's Heap Becomes Very Large and Never Reduce Down Xulei (Stone)
2017-11-15 11:00 ` Stefan Hajnoczi
2017-11-15 13:18 ` Paolo Bonzini
2017-11-16 1:43 ` Zhong Yang [this message]
2017-11-16 3:08 ` Xulei (Stone)
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=20171116014346.GA16015@yangzhon-Virtual \
--to=yang.zhong@intel.com \
--cc=anthony.xu@intel.com \
--cc=arei.gonglei@huawei.com \
--cc=berrange@redhat.com \
--cc=liujunjie23@huawei.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=stone.xulei@huawei.com \
--cc=wangxinxin.wang@huawei.com \
--cc=weidong.huang@huawei.com \
--cc=zhang.zhanghailiang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).