From: Paolo Bonzini <pbonzini@redhat.com>
To: Jitendra Kolhe <jitendra.kolhe@hpe.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kwolf@redhat.com" <kwolf@redhat.com>,
"peter.maydell@linaro.org" <peter.maydell@linaro.org>,
"armbru@redhat.com" <armbru@redhat.com>,
"MeenakshiSundaram,
Renganathan" <renganathan.meenakshisundaram@hpe.com>,
"Parthasarathy,
Mohan (HPE Servers)" <mohan_parthasarathy@hpe.com>
Subject: Re: [Qemu-devel] [PATCH RFC] mem-prealloc: Reduce large guest start-up and migration time.
Date: Fri, 3 Feb 2017 10:59:37 -0800 [thread overview]
Message-ID: <13f0f2e5-7c1d-b050-e3d6-0b504a803ae4@redhat.com> (raw)
In-Reply-To: <67bd733e-5974-327b-25f4-c83b8e379313@hpe.com>
On 02/02/2017 01:35, Jitendra Kolhe wrote:
>> Of course you'd still need the memset() trick if qemu was given
>> non-hugepages in combination with --mem-prealloc, as you don't
>> want to lock normal pages into ram permanently.
>>
> given above numbers, I think we can stick to memset() implementation for
> both hugepage and non-hugepage cases?
Yes, of course!
Paolo
prev parent reply other threads:[~2017-02-03 18:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 7:24 [Qemu-devel] [PATCH RFC] mem-prealloc: Reduce large guest start-up and migration time Jitendra Kolhe
2017-01-27 12:53 ` Juan Quintela
2017-01-27 13:06 ` Paolo Bonzini
2017-01-30 8:19 ` Jitendra Kolhe
2017-01-27 13:03 ` Dr. David Alan Gilbert
2017-01-30 8:32 ` Jitendra Kolhe
2017-02-07 7:44 ` Jitendra Kolhe
2017-01-27 13:26 ` Daniel P. Berrange
2017-02-02 9:35 ` Jitendra Kolhe
2017-02-03 18:59 ` Paolo Bonzini [this message]
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=13f0f2e5-7c1d-b050-e3d6-0b504a803ae4@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=jitendra.kolhe@hpe.com \
--cc=kwolf@redhat.com \
--cc=mohan_parthasarathy@hpe.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=renganathan.meenakshisundaram@hpe.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).