From: Scott Wood <scottwood@freescale.com>
To: Kenneth Johansson <kenneth@southpole.se>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: 5121 cache handling.
Date: Mon, 10 Aug 2009 15:26:16 -0500 [thread overview]
Message-ID: <4A808268.6000107@freescale.com> (raw)
In-Reply-To: <1249935384.7077.35.camel@localhost>
Kenneth Johansson wrote:
> But the code allocate the 52KB buffer with vmalloc that cant be right as
> cache is stored with physical address the 52KB data need to be 52KB
> continuous in physical address and vmalloc do not guarantee that.
Yeah, that looks like a bug.
>>> should not the framebuffer be marked as cache write through. that is the
>>> W bit should be set in the tlb mapping. Why is this not done ? is that
>>> feature also not working on 5121 ??
>> It probably would have been too slow.
>
> how much slower would write through be ? I thought it was not that big
> of a difference from copy back.
It's a big difference if you're writing out an entire cache line of data
anyway, but because of write-through it goes out one word at a time
without bursting.
-Scott
next prev parent reply other threads:[~2009-08-10 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 12:53 5121 cache handling Kenneth Johansson
2009-08-07 19:56 ` Scott Wood
2009-08-10 20:16 ` Kenneth Johansson
2009-08-10 20:26 ` Scott Wood [this message]
2009-08-10 20:45 ` Kenneth Johansson
2009-08-10 20:49 ` Scott Wood
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=4A808268.6000107@freescale.com \
--to=scottwood@freescale.com \
--cc=kenneth@southpole.se \
--cc=linuxppc-dev@ozlabs.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).