From: Jeff Keasler <keasler@llnl.gov>
To: linux-mm@kvack.org
Subject: L2 cache alignment and page coloring
Date: Tue, 14 Aug 2007 11:16:52 -0700 [thread overview]
Message-ID: <46C1F194.8080405@llnl.gov> (raw)
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.
--
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 reply other threads:[~2007-08-14 18:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 18:16 Jeff Keasler [this message]
2007-08-14 18:33 ` Chris Snook
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=46C1F194.8080405@llnl.gov \
--to=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