linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Steve Rossi <srossi@labs.mot.com>
Cc: Embedded Linux PPC List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: mmap & no cache regions
Date: Fri, 16 Nov 2001 00:39:23 -0500	[thread overview]
Message-ID: <3BF4A68B.5080803@embeddededge.com> (raw)
In-Reply-To: 3BF1939A.B96072AC@labs.mot.com


Steve Rossi wrote:

> .....I learned that consistent_alloc is not sufficent to
> guarantee cache coherency on the mmaped region

Well, it has no clue about what you are doing.  It's purpose is to
ensure the kernel's mapping of that page is set properly.

> .... - in fact I had to mark
> these pages PAGE_NO_CACHE in the user space application's memory map as
> well.

Yep, that's because the kernel and applications have their own page
tables and page attributes.

> .....- but is it safe
> to assume that the application's memory map will be destroyed so I don't
> have to worry about marking the pages in that map as cacheable again?

I was about to write a couple of pages when it is best to answer this
with a simple "yes."  When the application releases this space, the page
tables are simply destroyed.  The kernel does it's weird attribute change
because it doesn't really "release" the page as an application does.  That's
all I'll say for now :-).

Thanks.


	-- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-11-16  5:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-13 21:41 mmap & no cache regions Steve Rossi
2001-11-16  5:39 ` Dan Malek [this message]

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=3BF4A68B.5080803@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=srossi@labs.mot.com \
    /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).