linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: joakim.tjernlund@lumentis.se
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: WRITE_THRU  on 8xx missing
Date: Wed, 04 Sep 2002 22:12:13 -0400	[thread overview]
Message-ID: <3D76BD7D.8060102@embeddededge.com> (raw)
In-Reply-To: IGEFJKJNHJDCBKALBJLLMEDAFGAA.joakim.tjernlund@lumentis.se


Joakim Tjernlund wrote:

> I just noticed that _PAGE_WRITETHRU is defined in the linuxppc_2_4 tree but not in
> the linuxppc_2_4_devel tree, which is the one I am using :-(. Has this "function" been removed ,
> never to return or is the devel tree in a flux now for mpc8xx?

I don't know what we will do.  We always seems to be running out of control bits
in the PTE, so this is the first one to go if we need one for something else.
The writethrough mode is also a pain to support dynamically because it requires
special code in the tlb miss exception to load/clear bits in the PMD/L1 descriptor.
Adding this code nearly doubles the size of the exception handler, when you want
minimal instructions, for a feature (almost) no one uses.  At best, the writethrough
mode may return when I finish the large pages someday, and will be a special case
that covers a modulo 4M space on a 4M boundary (which I don't yet know how we
would allocate).

For burst flash, I suggest you read the archives for a discussion where you
double map the cache into a copyback mode space read and an uncached space
for write.  You will then invalidate during a write operation.  This would
maximize performance and require no VM or cache management changes.


>>I want to use this mapping to do burst reads but single writes for a flash device.

Are you sure writethough mode will do this?  I don't think it will as I believe
any cache enabled mode will burst.  To prevent burst you have to run with
caches disabled or have it inhibited in the memory controller.  Check it out.

Thanks.


	-- Dan


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

  reply	other threads:[~2002-09-05  2:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-29  1:39 8xx's IMMR can not be 0x12200000? caokai
2002-08-29  5:37 ` Dan Malek
2002-09-04 13:20   ` WRITE_THRU on 8xx missing Joakim Tjernlund
2002-09-04 22:27     ` Joakim Tjernlund
2002-09-05  2:12       ` Dan Malek [this message]
2002-09-05  7:28         ` Joakim Tjernlund

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=3D76BD7D.8060102@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=joakim.tjernlund@lumentis.se \
    --cc=linuxppc-embedded@lists.linuxppc.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).