_PAGE_WRITETHRU option in 8xx

_PAGE_WRITETHRU option in 8xx

[Anil Giri]

Hi,
  I am using linuxppx_2_4_20 from denx and i can;t find the _PAGE_WRITETHRU
option in include/asm-ppc/pgtable.h for 8xx. Is it replaced or ommitted?

Thanks
-Anil


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

Re: _PAGE_WRITETHRU option in 8xx

[Wolfgang Denk]

In message <1057841040.3f0d5f9022327@pop-mail.india.tejasnetworks.com> you wrote:
>
>   I am using linuxppx_2_4_20 from denx and i can;t find the _PAGE_WRITETHRU
> option in include/asm-ppc/pgtable.h for 8xx. Is it replaced or ommitted?

You must be using some different source tree. This is what I see:

	-> grep PAGE_WRITETHRU include/asm-ppc/pgtable.h
	#define _PAGE_WRITETHRU 0x008   /* W: caching is write-through */
	#define _PAGE_WRITETHRU 0x00000800              /* H: W bit */
	#define _PAGE_WRITETHRU 0x040   /* W: cache write-through */



Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
"Here's a fish hangs in the net like a poor man's right in  the  law.
'Twill hardly come out."     - Shakespeare, Pericles, Act II, Scene 1

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

Re: _PAGE_WRITETHRU option in 8xx

[Dan Malek]

Anil Giri wrote:

>   I am using linuxppx_2_4_20 from denx and i can;t find the _PAGE_WRITETHRU
> option in include/asm-ppc/pgtable.h for 8xx. Is it replaced or ommitted?

Write through cache mode per page on 8xx is not easy to set.  It requires
additonal overhead in the TLB Miss handler that will affect all page misses
and is a performance loss for all applications.  Additionally, you can't
arbitrarily set this mode on a page because it causes conflicting cache
modes in the VM map.  You would have to add yet another special memory
space and management functions like we have for managing DMA coherent memory.

 From a systems engineering perspective, write through cache is seldom a
performance benefit.  For small address ranges and access, it is better to
use uncached memory because you don't replace lines more useful to others.
If you are heavily accessing cached data that must be synchronized with
other operations, copyback with explicit cache push provides better performance.

For debugging, you can globally select write through instead of copyback,
and obviously I'm not recommending using write through for normal operation.


	-- Dan


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