From: Alexander Graf <agraf@suse.de>
To: Paul Mackerras <paulus@samba.org>
Cc: kvm-ppc@vger.kernel.org, KVM list <kvm@vger.kernel.org>,
linux-mm@kvack.org, mina86@mina86.com
Subject: Re: [PATCH 0/3] KVM: PPC: Book3S HV: More flexible allocator for linear memory
Date: Tue, 30 Oct 2012 10:12:19 +0100 [thread overview]
Message-ID: <807B8637-B694-42A3-B615-97AC5E24B26E@suse.de> (raw)
In-Reply-To: <20121026011733.GA31394@drongo>
On 26.10.2012, at 03:17, Paul Mackerras wrote:
> On Fri, Sep 14, 2012 at 03:15:32PM +0200, Alexander Graf wrote:
>>
>> On 14.09.2012, at 14:45, Paul Mackerras wrote:
>>
>>> On Fri, Sep 14, 2012 at 02:13:37PM +0200, Alexander Graf wrote:
>>>
>>>> So do you think it makes more sense to reimplement a large page allocator in KVM, as this patch set does, or improve CMA to get us really big chunks of linear memory?
>>>>
>>>> Let's ask the Linux mm guys too :). Maybe they have an idea.
>>>
>>> I asked the authors of CMA, and apparently it's not limited to
>>> MAX_ORDER as I feared. It has the advantage that the memory can be
>>> used for other things such as page cache when it's not needed, but not
>>> for immovable allocations such as kmalloc. I'm going to try it out.
>>> It will need a patch to increase the maximum alignment it allows.
>>
>> Awesome. Thanks a lot. I'd really prefer if we can stick to generic Linux solutions rather than invent our own :).
>
> Turns out there is a difficulty with this. When we have a guest page
> that we want to pin in memory, and that page happens to have been
> allocated within the CMA region, we would need to migrate it out of
> the CMA region before pinning it, since otherwise it would reduce the
> amount of contiguous memory available. But it appears that there
> isn't any way to do that.
How does this work for other users of CMA? I can't possibly believe that we only ever want a static amount of contiguous memory on the system.
Alex
--
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>
prev parent reply other threads:[~2012-10-30 9:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120912003427.GH32642@bloggs.ozlabs.ibm.com>
[not found] ` <9650229C-2512-4684-98EC-6E252E47C4A9@suse.de>
[not found] ` <20120914081140.GC15028@bloggs.ozlabs.ibm.com>
2012-09-14 12:13 ` Alexander Graf
2012-09-14 12:45 ` Paul Mackerras
2012-09-14 13:15 ` Alexander Graf
2012-10-26 1:17 ` Paul Mackerras
2012-10-30 9:12 ` Alexander Graf [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=807B8637-B694-42A3-B615-97AC5E24B26E@suse.de \
--to=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mina86@mina86.com \
--cc=paulus@samba.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