Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jeff Harrell <jharrell@ti.com>
To: sgi-mips <linux@cthulhu.engr.sgi.com>
Cc: Ralf Baechle <ralf@oss.sgi.com>, bbrown <bbrown@ti.com>,
	vwells <vwells@ti.com>, kmcdonald <kmcdonald@ti.com>,
	mhassler <mhassler@ti.com>
Subject: Question concerning cache coherency
Date: Wed, 19 Jan 2000 10:00:11 -0700	[thread overview]
Message-ID: <3885ED9B.C8969F26@ti.com> (raw)

I have an interesting issue that I would like to run past the MIPS/Linux
newsgroup.  I am
currently porting the MIPS/Linux code to a development board that has a
IDT64475 MIPS
core (64-bit R4xxx core).  I notice that this part does not have any
method of maintaining
cache coherency (i.e., no hardware support for cache coherency).  It is
highly likely that we
will be plugging in a network card on a PCI bus that would be DMA'ing to
a shared memory
space in SDRAM.  I assume that the problem of cache coherency is fixed
by mapping the shared
memory as uncached.  I have not dug into the network drivers (or the
kernel) enough to know whether
this is how the problem is addressed on typical MIPS architectures.  I
guess I have two questions
related to this issue;  Do devices that DMA, typically access uncached
memory  and if so, is a second buffer
required to copy from kernel to user space?  The second question is
concerning the performance hit in
running out of uncached memory,  Have people seen significant
performance degradation when
using uncached memory.  Any insight that anybody can provide would be
greatly appreciated.

Thanks,
Jeff


--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Jeff Harrell                    Work:  (801) 619-6104
Broadband Access group/TI
jharrell@ti.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

             reply	other threads:[~2000-01-19 17:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-19 17:00 Jeff Harrell [this message]
2000-01-19 23:22 ` Question concerning cache coherency Ralf Baechle
  -- strict thread matches above, loose matches on Subject: below --
2000-01-20  0:49 Kevin D. Kissell

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=3885ED9B.C8969F26@ti.com \
    --to=jharrell@ti.com \
    --cc=bbrown@ti.com \
    --cc=kmcdonald@ti.com \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=mhassler@ti.com \
    --cc=ralf@oss.sgi.com \
    --cc=vwells@ti.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