linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: budheej@gmail.com (Budhee Jamaich)
To: linux-arm-kernel@lists.infradead.org
Subject: mapping uncached memory
Date: Wed, 17 Mar 2010 01:17:45 +0200	[thread overview]
Message-ID: <57314e841003161617l53dc3a50la969369f0161ccdd@mail.gmail.com> (raw)

hello,

we are looking for ways to map memory as uncached,
so remote devices reading/writing to this memory will see consistent data.


these are the alternatives we currently see:


1. clean cache after every write to the memory (/invalidate the cache
before every read)

this can be done using dmac_clean/inv_range and outer_clean/inv_range
just like in dma_cache_maint.
btw - what's the difference between the dmac_* and the outer_*
functions ? why both are needed ?

disadvantage: this will be needed to be called before/after every memory access





2. use pgprot_noncached when assigning vma->vm_page_prot in our
driver's mmap method


will that really work ? all memory accesses will be uncached ?








3. use dma_alloc_coherent in some way

cons: documentation says we still need to use cache clean/inv
operations, so this might not really be of any advantage. but if that
is so, what's the idea behind coherent pools of memory ? how does it
work at all ?




what do you say ?


thank you all very much in advance
budhee

             reply	other threads:[~2010-03-16 23:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-16 23:17 Budhee Jamaich [this message]
2010-03-16 23:54 ` mapping uncached memory Russell King - ARM Linux
2010-03-17  4:34   ` Jamie Lokier
2010-03-17  8:02   ` Budhee Jamaich
2010-03-17  8:15     ` Russell King - ARM Linux
2010-03-17  9:09       ` Budhee Jamaich
2010-03-17 21:26       ` Colin Cross
2010-03-17 22:03         ` Catalin Marinas
2010-03-23 12:22   ` Budhee Jamaich

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=57314e841003161617l53dc3a50la969369f0161ccdd@mail.gmail.com \
    --to=budheej@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).