From: Ralf Baechle <ralf@linux-mips.org>
To: Teresa Tao <Teresat@tridentmicro.com>
Cc: linux-mips@linux-mips.org
Subject: Re: mmap'ed memory cacheable or uncheable
Date: Thu, 31 Jul 2003 13:31:21 +0200 [thread overview]
Message-ID: <20030731113121.GB2718@linux-mips.org> (raw)
In-Reply-To: <61F6477DE6BED311B69F009027C3F58403AA3969@EXCHANGE>
On Thu, Jul 24, 2003 at 08:26:59PM -0700, Teresa Tao wrote:
> I got a question regarding the mmap'ed memory. Is the mmap'ed memory
> cacheable or uncheable? My driver just use the remap_page_range to map
> a reserved physical memory.
Mmap(2) creates cachable mappings for everything below the highest memory
address and uncached above that. That's a somewhat naive mechanism
which fails a few systems but somehow nobody did complain so far ...
Ralf
next prev parent reply other threads:[~2003-07-31 11:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 3:26 mmap'ed memory cacheable or uncheable Teresa Tao
2003-07-25 3:26 ` Teresa Tao
2003-07-25 22:02 ` Jun Sun
2003-07-31 11:31 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-25 22:52 Teresa Tao
2003-07-25 22:52 ` Teresa Tao
2003-07-28 21:24 ` Jun Sun
2003-07-29 16:09 ` Maciej W. Rozycki
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=20030731113121.GB2718@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Teresat@tridentmicro.com \
--cc=linux-mips@linux-mips.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