From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Christoph Lameter <clameter@sgi.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-mm@kvack.org, Andy Whitcroft <apw@shadowen.org>,
Dave Hansen <haveblue@us.ibm.com>
Subject: Re: [PATCH] Get rid of zone_table V2
Date: Wed, 20 Sep 2006 02:45:34 +1000 [thread overview]
Message-ID: <45101EAE.2070303@yahoo.com.au> (raw)
In-Reply-To: <4510196A.5090306@yahoo.com.au>
Nick Piggin wrote:
> Christoph Lameter wrote:
>> Would be okay to grow the size of struct zone to the next power of 2
>> bytes?
>
>
> I'd say yes: it is only memory we're talking about here, not cachelines,
> because the whole thing is cacheline aligned up the wazoo anyway. Let's
> see, on your example system that would take up an extra 896 bytes per
> struct zone... not too bad.
>
> And it is a better solution than shrinking because it will work on all
> architectures and configurations.
BTW. I wonder why gcc isn't using two shifts in your example? Not that
I think it would be great even if it were, because subtle differences
could cause that to become more shifts...
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
--
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:[~2006-09-19 16:45 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 19:21 Christoph Lameter
2006-09-18 20:28 ` Andrew Morton
2006-09-18 22:51 ` Christoph Lameter
2006-09-18 23:15 ` Andrew Morton
2006-09-18 23:46 ` Christoph Lameter
2006-09-18 23:58 ` Andrew Morton
2006-09-19 0:08 ` Christoph Lameter
2006-09-19 0:14 ` Christoph Lameter
2006-09-19 0:31 ` Andrew Morton
2006-09-19 1:20 ` Christoph Lameter
2006-09-19 6:12 ` Christoph Lameter
2006-09-19 6:33 ` Andrew Morton
2006-09-19 14:10 ` Christoph Lameter
2006-09-19 15:38 ` Andrew Morton
2006-09-19 15:41 ` Christoph Lameter
2006-09-19 16:23 ` Nick Piggin
2006-09-19 16:45 ` Nick Piggin [this message]
2006-09-19 17:50 ` Christoph Lameter
2006-09-19 18:24 ` Andi Kleen
2006-09-19 16:17 ` Nick Piggin
2006-09-24 10:06 ` Andrew Morton
2006-09-24 16:58 ` Christoph Lameter
2006-09-27 9:19 ` Andrew Morton
2006-09-27 9:26 ` Andy Whitcroft
2006-09-27 11:23 ` [PATCH] zone table removal miss merge Andy Whitcroft
2006-09-27 16:19 ` Christoph Lameter
2006-09-27 11:27 ` [PATCH] Get rid of zone_table V2 Andy Whitcroft
2006-09-27 16:24 ` Andrew Morton
2006-09-30 18:47 ` Christoph Lameter
2006-09-30 18:48 ` Christoph Lameter
2006-09-30 20:08 ` Andrew Morton
2006-10-02 15:57 ` Christoph Lameter
2006-10-02 17:10 ` Christoph Lameter
2006-10-04 10:10 ` Andy Whitcroft
2006-10-06 14:45 ` [PATCH] zoneid fix up calculations for ZONEID_PGSHIFT Andy Whitcroft
2006-10-06 17:00 ` 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=45101EAE.2070303@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=clameter@sgi.com \
--cc=haveblue@us.ibm.com \
--cc=linux-mm@kvack.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