From: Michal Hocko <mhocko@suse.cz>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com,
andi@firstfloor.org, akpm@linux-foundation.org,
linux-mm@kvack.org, kamezawa.hiroyuki@gmail.com,
hannes@cmpxchg.org, yinghan@google.com
Subject: Re: [PATCH 2/2] Drivers: hv: balloon: Support 2M page allocations for ballooning
Date: Mon, 18 Mar 2013 11:52:57 +0100 [thread overview]
Message-ID: <20130318105257.GG10192@dhcp22.suse.cz> (raw)
In-Reply-To: <1363470125-24606-2-git-send-email-kys@microsoft.com>
On Sat 16-03-13 14:42:05, K. Y. Srinivasan wrote:
> While ballooning memory out of the guest, attempt 2M allocations first.
> If 2M allocations fail, then go for 4K allocations. In cases where we
> have performed 2M allocations, split this 2M page so that we can free this
> page at 4K granularity (when the host returns the memory).
Maybe I am missing something but what is the advantage of 2M allocation
when you split it up immediately so you are not using it as a huge page?
[...]
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-03-18 10:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-16 21:41 [PATCH 0/2] Drivers: hv: balloon K. Y. Srinivasan
2013-03-16 21:42 ` [PATCH 1/2] mm: Export split_page() K. Y. Srinivasan
2013-03-16 21:42 ` [PATCH 2/2] Drivers: hv: balloon: Support 2M page allocations for ballooning K. Y. Srinivasan
2013-03-18 10:52 ` Michal Hocko [this message]
2013-03-18 11:01 ` Michal Hocko
2013-03-18 13:44 ` KY Srinivasan
2013-03-18 14:13 ` Michal Hocko
2013-03-18 15:08 ` KY Srinivasan
2013-03-18 16:29 ` Michal Hocko
2013-03-18 11:03 ` [PATCH 1/2] mm: Export split_page() Michal Hocko
2013-03-18 13:28 ` KY Srinivasan
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=20130318105257.GG10192@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyuki@gmail.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=olaf@aepfle.de \
--cc=yinghan@google.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