From: Manfred Spraul <manfred@colorfullife.com>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: Alok Kataria <alokk@calsoftinc.com>,
Petr Vandrovec <vandrove@vc.cvut.cz>,
linux-kernel@vger.kernel.org, linux-mm@vger.kernel.org
Subject: Re: [RFC] Use compound pages for higher order slab allocations.
Date: Sat, 03 Dec 2005 20:10:05 +0100 [thread overview]
Message-ID: <4391ED8D.1040104@colorfullife.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0511301334450.20244@schroedinger.engr.sgi.com>
Christoph Lameter wrote:
>+static inline struct page *virt_to_compound_page(const void *addr)
>+{
>+ struct page * page = virt_to_page(addr);
>+
>+ if (PageCompound(page))
>+ page = (struct page *)page_private(page);
>+
>
>
This would end up in every kmem_cache_free/kfree call. Is it really
worth the effort, are the high order allocation a problem?
I'm against such a change without a clear proof that just using high
order allocations is not possible.
--
Manfred
next prev parent reply other threads:[~2005-12-03 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 21:37 [RFC] Use compound pages for higher order slab allocations Christoph Lameter
2005-12-03 19:10 ` Manfred Spraul [this message]
2005-12-05 17:03 ` Christoph Lameter
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=4391ED8D.1040104@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=alokk@calsoftinc.com \
--cc=clameter@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/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