From: Chris Zankel <zankel@tensilica.com>
To: linux-mm@kvack.org
Subject: SMP and cache-aliasing.
Date: Wed, 25 Apr 2007 10:15:32 -0700 [thread overview]
Message-ID: <462F8CB4.4070907@tensilica.com> (raw)
Hi,
Sorry for the intrusion, but maybe someone with more insight in linux
memory-management can give me a brief hint about the following:
In an SMP system with cache-aliasing, is it possible that the same
physical page is mapped to two or more virtual addresses of different
'color'?
On a single processor system this doesn't happen. Shared pages are
always allocated in a way to avoid cache-aliasing and non-shared pages
are only mapped once in user-space.
I guess that leaves kernel space. Is it possible that the kernel running
on the two different processors maps the same physical address to pages
of different 'color' in kernel space?
Thank you for any input,
-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-04-25 17:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=462F8CB4.4070907@tensilica.com \
--to=zankel@tensilica.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