From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alexander Graf <agraf@suse.de>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
paulus@samba.org, m.szyprowski@samsung.com, mina86@mina86.com,
linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org,
kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH -V3 2/4] powerpc/kvm: Contiguous memory allocator based hash page table allocation
Date: Tue, 02 Jul 2013 22:28:29 +0000 [thread overview]
Message-ID: <1372804109.4122.25.camel@pasglop> (raw)
In-Reply-To: <51D2EDD7.9060205@suse.de>
On Tue, 2013-07-02 at 17:12 +0200, Alexander Graf wrote:
> Is CMA a mandatory option in the kernel? Or can it be optionally
> disabled? If it can be disabled, we should keep the preallocated
> fallback case around for systems that have CMA disabled.
Why ? More junk code to keep around ...
If CMA is disabled, we can limit ourselves to dynamic allocation (with
limitation to 16M hash table).
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alexander Graf <agraf@suse.de>
Cc: kvm-ppc@vger.kernel.org, kvm@vger.kernel.org, mina86@mina86.com,
linux-mm@kvack.org, paulus@samba.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, m.szyprowski@samsung.com
Subject: Re: [PATCH -V3 2/4] powerpc/kvm: Contiguous memory allocator based hash page table allocation
Date: Wed, 03 Jul 2013 08:28:29 +1000 [thread overview]
Message-ID: <1372804109.4122.25.camel@pasglop> (raw)
In-Reply-To: <51D2EDD7.9060205@suse.de>
On Tue, 2013-07-02 at 17:12 +0200, Alexander Graf wrote:
> Is CMA a mandatory option in the kernel? Or can it be optionally
> disabled? If it can be disabled, we should keep the preallocated
> fallback case around for systems that have CMA disabled.
Why ? More junk code to keep around ...
If CMA is disabled, we can limit ourselves to dynamic allocation (with
limitation to 16M hash table).
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alexander Graf <agraf@suse.de>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
paulus@samba.org, m.szyprowski@samsung.com, mina86@mina86.com,
linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org,
kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH -V3 2/4] powerpc/kvm: Contiguous memory allocator based hash page table allocation
Date: Wed, 03 Jul 2013 08:28:29 +1000 [thread overview]
Message-ID: <1372804109.4122.25.camel@pasglop> (raw)
In-Reply-To: <51D2EDD7.9060205@suse.de>
On Tue, 2013-07-02 at 17:12 +0200, Alexander Graf wrote:
> Is CMA a mandatory option in the kernel? Or can it be optionally
> disabled? If it can be disabled, we should keep the preallocated
> fallback case around for systems that have CMA disabled.
Why ? More junk code to keep around ...
If CMA is disabled, we can limit ourselves to dynamic allocation (with
limitation to 16M hash table).
Cheers,
Ben.
--
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-07-02 22:28 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 5:45 [PATCH -V3 1/4] mm/cma: Move dma contiguous changes into a seperate config Aneesh Kumar K.V
2013-07-02 5:57 ` Aneesh Kumar K.V
2013-07-02 5:45 ` Aneesh Kumar K.V
2013-07-02 5:45 ` [PATCH -V3 2/4] powerpc/kvm: Contiguous memory allocator based hash page table allocation Aneesh Kumar K.V
2013-07-02 5:57 ` Aneesh Kumar K.V
2013-07-02 5:45 ` Aneesh Kumar K.V
2013-07-02 15:12 ` Alexander Graf
2013-07-02 15:12 ` Alexander Graf
2013-07-02 15:12 ` Alexander Graf
2013-07-02 15:12 ` Alexander Graf
2013-07-02 15:31 ` Aneesh Kumar K.V
2013-07-02 15:43 ` Aneesh Kumar K.V
2013-07-02 15:31 ` Aneesh Kumar K.V
2013-07-02 15:31 ` Aneesh Kumar K.V
2013-07-02 15:32 ` Alexander Graf
2013-07-02 15:32 ` Alexander Graf
2013-07-02 15:32 ` Alexander Graf
2013-07-02 15:32 ` Alexander Graf
2013-07-02 22:28 ` Benjamin Herrenschmidt [this message]
2013-07-02 22:28 ` Benjamin Herrenschmidt
2013-07-02 22:28 ` Benjamin Herrenschmidt
2013-07-02 22:31 ` Alexander Graf
2013-07-02 22:31 ` Alexander Graf
2013-07-02 22:31 ` Alexander Graf
2013-07-03 6:15 ` Paul Mackerras
2013-07-03 6:15 ` Paul Mackerras
2013-07-03 6:15 ` Paul Mackerras
2013-07-02 5:45 ` [PATCH -V3 3/4] powerpc/kvm: Contiguous memory allocator based RMA allocation Aneesh Kumar K.V
2013-07-02 5:57 ` Aneesh Kumar K.V
2013-07-02 5:45 ` Aneesh Kumar K.V
2013-07-02 15:17 ` Alexander Graf
2013-07-02 15:17 ` Alexander Graf
2013-07-02 15:17 ` Alexander Graf
2013-07-02 15:17 ` Alexander Graf
2013-07-02 15:29 ` Aneesh Kumar K.V
2013-07-02 15:41 ` Aneesh Kumar K.V
2013-07-02 15:29 ` Aneesh Kumar K.V
2013-07-02 15:29 ` Aneesh Kumar K.V
2013-07-02 15:32 ` Alexander Graf
2013-07-02 15:32 ` Alexander Graf
2013-07-02 15:32 ` Alexander Graf
2013-07-02 15:32 ` Alexander Graf
2013-07-02 16:28 ` Aneesh Kumar K.V
2013-07-02 16:40 ` Aneesh Kumar K.V
2013-07-02 16:28 ` Aneesh Kumar K.V
2013-07-02 16:36 ` Alexander Graf
2013-07-02 16:36 ` Alexander Graf
2013-07-02 16:36 ` Alexander Graf
2013-07-02 16:36 ` Alexander Graf
2013-07-02 5:45 ` [PATCH -V3 4/4] powerpc/kvm: Use 256K chunk to track both RMA and hash page table allocation Aneesh Kumar K.V
2013-07-02 5:57 ` Aneesh Kumar K.V
2013-07-02 5:45 ` Aneesh Kumar K.V
2013-07-02 6:29 ` virtual machine windows freeze on copy data to an samba share Marko Weber | ZBF
2013-07-03 6:16 ` [PATCH -V3 4/4] powerpc/kvm: Use 256K chunk to track both RMA and hash page table allocation Paul Mackerras
2013-07-03 6:16 ` Paul Mackerras
2013-07-03 6:16 ` Paul Mackerras
2013-07-03 6:16 ` Paul Mackerras
2013-07-02 8:20 ` [PATCH -V3 1/4] mm/cma: Move dma contiguous changes into a seperate config Marek Szyprowski
2013-07-02 8:20 ` Marek Szyprowski
2013-07-02 8:20 ` Marek Szyprowski
2013-07-02 15:33 ` Aneesh Kumar K.V
2013-07-02 15:45 ` Aneesh Kumar K.V
2013-07-02 15:33 ` Aneesh Kumar K.V
2013-07-08 14:21 ` Alexander Graf
2013-07-08 14:21 ` Alexander Graf
2013-07-08 14:21 ` Alexander Graf
2013-07-08 14:21 ` Alexander Graf
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=1372804109.4122.25.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=agraf@suse.de \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=m.szyprowski@samsung.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.