From: Christoph Lameter <cl@linux.com>
To: Hugh Dickins <hughd@google.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-mm@kvack.org
Subject: Re: 4.12-rc ppc64 4k-page needs costly allocations
Date: Fri, 2 Jun 2017 09:32:15 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.20.1706020931080.28919@east.gentwo.org> (raw)
In-Reply-To: <alpine.LSU.2.11.1706011128490.3622@eggly.anvils>
On Thu, 1 Jun 2017, Hugh Dickins wrote:
> Thanks a lot for working that out. Makes sense, fully understood now,
> nothing to worry about (though makes one wonder whether it's efficient
> to use ctors on high-alignment caches; or whether an internal "zero-me"
> ctor would be useful).
Use kzalloc to zero it. And here is another example of using slab
allocations for page frames. Use the page allocator for this? The page
allocator is there for allocating page frames. The slab allocator main
purpose is to allocate small objects....
--
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:[~2017-06-02 14:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 19:43 Hugh Dickins
2017-05-31 6:46 ` Michael Ellerman
2017-05-31 14:09 ` Christoph Lameter
2017-05-31 18:44 ` Hugh Dickins
2017-05-31 19:02 ` Mathieu Malaterre
2017-06-01 15:31 ` Christoph Lameter
2017-06-01 17:22 ` Hugh Dickins
2017-06-01 18:16 ` Christoph Lameter
2017-06-01 18:37 ` Hugh Dickins
2017-06-02 3:09 ` Michael Ellerman
2017-06-02 4:00 ` Hugh Dickins
2017-06-02 14:33 ` Christoph Lameter
2017-06-08 5:44 ` Michael Ellerman
2017-06-02 14:32 ` Christoph Lameter [this message]
2017-06-08 5:52 ` Michael Ellerman
2017-05-31 14:06 ` Christoph Lameter
2017-06-01 4:19 ` Aneesh Kumar K.V
2017-06-01 16:57 ` Hugh Dickins
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=alpine.DEB.2.20.1706020931080.28919@east.gentwo.org \
--to=cl@linux.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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