From: Rohit Seth <rohitseth@google.com>
To: Paul Jackson <pj@sgi.com>
Cc: akpm@osdl.org, nickpiggin@yahoo.com.au, ak@suse.de,
linux-mm@kvack.org, holt@sgi.com, mbligh@google.com,
rientjes@google.com, menage@google.com, clameter@sgi.com
Subject: Re: [PATCH] memory page_alloc zonelist caching speedup aligncache
Date: Wed, 18 Oct 2006 08:35:37 -0700 [thread overview]
Message-ID: <1161185737.582.326.camel@galaxy.corp.google.com> (raw)
In-Reply-To: <20061018081440.18477.10664.sendpatchset@sam.engr.sgi.com>
On Wed, 2006-10-18 at 01:14 -0700, Paul Jackson wrote:
> From: Paul Jackson <pj@sgi.com>
>
> Avoid frequent writes to the zonelist zones[] array, which are
> read-only after initial setup, by putting the zonelist_cache on
> a separate cacheline.
>
> Signed-off-by: Paul Jackson <pj@sgi.com>
>
> ---
>
> include/linux/mmzone.h | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletion(-)
>
> --- 2.6.19-rc2-mm1.orig/include/linux/mmzone.h 2006-10-17 17:19:22.000000000 -0700
> +++ 2.6.19-rc2-mm1/include/linux/mmzone.h 2006-10-17 17:31:31.000000000 -0700
> @@ -396,7 +396,8 @@ struct zonelist {
> struct zonelist_cache *zlcache_ptr; // NULL or &zlcache
> struct zone *zones[MAX_ZONES_PER_ZONELIST + 1]; // NULL delimited
> #ifdef CONFIG_NUMA
> - struct zonelist_cache zlcache; // optional ...
> + /* Keep written zonelist_cache off read-only zones[] cache lines */
> + struct zonelist_cache zlcache ____cacheline_aligned; // optional ...
> #endif
> };
>
>
Wouldn't it be better to have the read mostly field z_to_n defined first
in zonelist_cache (and define the BITMAP at the end).
-rohit
--
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:[~2006-10-18 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 8:14 Paul Jackson, Paul Jackson
2006-10-18 15:35 ` Rohit Seth [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=1161185737.582.326.camel@galaxy.corp.google.com \
--to=rohitseth@google.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=holt@sgi.com \
--cc=linux-mm@kvack.org \
--cc=mbligh@google.com \
--cc=menage@google.com \
--cc=nickpiggin@yahoo.com.au \
--cc=pj@sgi.com \
--cc=rientjes@google.com \
/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