| To: | Teresa Tao <Teresat@tridentmicro.com> |
|---|---|
| Subject: | Re: mmap'ed memory cacheable or uncheable |
| From: | Jun Sun <jsun@mvista.com> |
| Date: | Fri, 25 Jul 2003 15:02:24 -0700 |
| Cc: | linux-mips@linux-mips.org, jsun@mvista.com |
| In-reply-to: | <61F6477DE6BED311B69F009027C3F58403AA3969@EXCHANGE>; from Teresat@tridentmicro.com on Thu, Jul 24, 2003 at 08:26:59PM -0700 |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <61F6477DE6BED311B69F009027C3F58403AA3969@EXCHANGE> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.2.5i |
On Thu, Jul 24, 2003 at 08:26:59PM -0700, Teresa Tao wrote: > Hi there, > > 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. > I am pretty much sure it is cached, although I can't pin down exactly where in the mm subsystem it does so - I have had cache bugs related to mmap(). Jun |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | No mouse support for Indy in 2.5.75 ?, Frank=20F=F6rstemann |
|---|---|
| Next by Date: | RE: mmap'ed memory cacheable or uncheable, Teresa Tao |
| Previous by Thread: | mmap'ed memory cacheable or uncheable, Teresa Tao |
| Next by Thread: | Re: mmap'ed memory cacheable or uncheable, Ralf Baechle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |