linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Chris Snook <csnook@redhat.com>
To: keasler@llnl.gov
Cc: linux-mm@kvack.org
Subject: Re: L2 cache alignment and page coloring
Date: Tue, 14 Aug 2007 14:33:23 -0400	[thread overview]
Message-ID: <46C1F573.4000403@redhat.com> (raw)
In-Reply-To: <46C1F194.8080405@llnl.gov>

Jeff Keasler wrote:
> Hi,
> 
> I work in an HPC environment where we run a process with a tight inner 
> loop (entirely contained in the I-cache) to work on large quantities of 
> data.  We've reduced system services to minimize our process getting 
> swapped out.
> 
> I am concerned that using malloc(L2_CACHE_SIZE) in user space is mapping 
> the underlying physical pages such that they do not form a cover of the 
> L2 cache (i.e. several physical pages are aliasing into the same part of 
> the L2 cache).
> 
> Are there any tricks available to force a more cache friendly 
> virtual-to-physical mapping from user space?
> 
> Thanks,
> -Jeff
> 
> PS  Even better if it is likely to work for L3 cache.

There may be easier methods depending on your architecture, but if the memory 
region is contiguous in both virtual and physical memory, it's pretty much 
impossible for any set-associative cache implementation (even L3) to alias it 
inefficiently.  Therefore I suggest using hugepages.  Just make sure that either 
you're using CPUs with lots of hugepage TLB entries, or that you won't be using 
very many of them at once.

	-- Chris

--
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:[~2007-08-14 18:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-14 18:16 Jeff Keasler
2007-08-14 18:33 ` Chris Snook [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=46C1F573.4000403@redhat.com \
    --to=csnook@redhat.com \
    --cc=keasler@llnl.gov \
    --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