From: Paolo Bonzini <pbonzini@redhat.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [RFC] memory consumption of Qemu is twice as much as the previous version in KVM
Date: Mon, 22 May 2017 17:30:49 +0200 [thread overview]
Message-ID: <3570bfd4-e963-df19-9df6-5629e5e203af@redhat.com> (raw)
In-Reply-To: <33183CC9F5247A488A2544077AF19020DA2B24F2@DGGEMA505-MBX.china.huawei.com>
On 22/05/2017 17:11, Gonglei (Arei) wrote:
>> These are kernel allocations done by KVM when it gets the
>> KVM_SET_USER_MEMORY_REGION ioctl; of course the two memory maps
>> point to
>> the same userspace mmap-ed area.
>
> Oh? What's the mmapd-ed area you pointed?
I mean the MAP_ANON pages that back the guest memory.
> If the KVM allocate memory by vmalloc(), then it will occupy physical
> memory (non physically contiguous memory) IMO.
>
> We can get the information from /proc/meminfo:
>
> # cat /proc/meminfo |grep Vmalloc
> VmallocTotal: 34359738367 kB
> VmallocUsed: 532796 kB
> VmallocChunk: 34292018200 kB
>
> So I think this part of memory is double after that SMM commit. Right?
Yes.
Paolo
next prev parent reply other threads:[~2017-05-22 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 7:04 [Qemu-devel] [RFC] memory consumption of Qemu is twice as much as the previous version in KVM Gonglei (Arei)
2017-05-22 8:27 ` Paolo Bonzini
2017-05-22 8:32 ` Daniel P. Berrange
2017-05-22 8:40 ` Gonglei (Arei)
2017-05-22 9:17 ` Paolo Bonzini
2017-05-22 15:11 ` Gonglei (Arei)
2017-05-22 15:30 ` Paolo Bonzini [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-22 7:10 Gonglei (Arei)
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=3570bfd4-e963-df19-9df6-5629e5e203af@redhat.com \
--to=pbonzini@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=berrange@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/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).