linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Paul Jackson <pj@sgi.com>
Cc: holt@sgi.com, ak@suse.de, linux-mm@kvack.org, akpm@osdl.org,
	nickpiggin@yahoo.com.au, rientjes@google.com, mbligh@google.com,
	rohitseth@google.com, menage@google.com, clameter@sgi.com
Subject: Re: [TAKE] memory page_alloc zonelist caching speedup
Date: Mon, 16 Oct 2006 11:31:40 -0700	[thread overview]
Message-ID: <20061016113140.f5461567.pj@sgi.com> (raw)
In-Reply-To: <20061016095805.f7576230.pj@sgi.com>

And note that in the vast majority of cases, where the requested page
is available on the local node, there is no difference.

Only if we are forced to start scanning other nodes do we examine,
and once per-second zap, our node local cache of whether the other
nodes we scan were recently found to be full.

The classic parts of the zonelist zone arrays are still intact,
read-only, at the front of the struct zonelist.

The compact, node-local, periodically written zonelist cache is added
at the end of the zonelist struct, most likely in its own cache lines,
and lets us avoid node remote access to a larger set of more frequently
updated cache lines on each allocation request.

Only on configs with small, but greater than one, MAX_NUMNODES, is
there any chance of the zonelist cache being on the same cache line
as the class zone array.  As best as I can tell from a quick grep,
that would be avr32, arm/collie, powerpc/cell, and powerpc/pseries,
which have NODES_SHIFT values between 2 and 4, and various L1 cache
line sizes between 16 and 128 bytes.

Perhaps I should add a ____cacheline_aligned qualifier to the
zonelist_cache struct, for these arch's?

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

--
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>

  reply	other threads:[~2006-10-16 18:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10  8:14 Paul Jackson
2006-10-16  9:34 ` Andi Kleen
2006-10-16 10:26   ` Paul Jackson
2006-10-16 11:25     ` Robin Holt
2006-10-16 16:58       ` Paul Jackson
2006-10-16 18:31         ` Paul Jackson [this message]
2006-11-08 10:21 ` Paul Jackson

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=20061016113140.f5461567.pj@sgi.com \
    --to=pj@sgi.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=rientjes@google.com \
    --cc=rohitseth@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