From: Dan Malek <dan@embeddededge.com>
To: Donald White <dbwhite@asu.edu>
Cc: linux-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Question about porting VxWorks driver
Date: Thu, 03 Apr 2003 10:27:25 -0500 [thread overview]
Message-ID: <3E8C52DD.8050107@embeddededge.com> (raw)
In-Reply-To: 3E8BECA6.6060709@asu.edu
Donald White wrote:
> Is this the right approach for me to take? Does Linux support
> designating memory
> regions for writethrough caching? If it does, should I use it rather
> than doing
> what I am doing?
Writethough policies to I/O devices seems kind of weird. If there
is a performance advantage because you are treating the device like
memory and using it to store buffers you will soon read again (unchanged),
you are likely to see even higher performance if you allocate system
memory in copyback mode for this purpose and just copy the data to
the I/O device when necessary.
I suspect writethrough was used to avoid cache flushing operations,
but uncached would likely result in better system performance because
you aren't blowing away cache lines useful to other software in
the system.
Linux does not support writethrough attributes through any memory
management functions, it only selects between cached and uncached
policies. On 8xx, you can globally select all cached memory to be
writethrough (usually for debugging), and *all* ioremap() areas are uncached.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-04-03 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-03 8:11 Question about porting VxWorks driver Donald White
2003-04-03 15:27 ` Dan Malek [this message]
2003-04-03 15:41 ` Vladimir Gurevich
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=3E8C52DD.8050107@embeddededge.com \
--to=dan@embeddededge.com \
--cc=dbwhite@asu.edu \
--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).