All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista.com>
To: Adrian Cox <adrian@humboldt.co.uk>
Cc: Tom Rini <trini@kernel.crashing.org>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: Caching in the MPC107
Date: Tue, 10 Sep 2002 13:03:48 -0400	[thread overview]
Message-ID: <3D7E25F4.4CC00BF8@mvista.com> (raw)
In-Reply-To: 1031672735.2686.58.camel@newt


Adrian Cox wrote:

> I think the problem was only visible because the pcnet32 device polls a
> descriptor small enough to get cached in the MPC107, and no other PCI
> master is active to read this cache. I don't currently have access to a
> Sandpoint X3 to test this out on.
>
> The problem seems to be a logical consequence of the documented and
> correct behaviour of the MPC107 and the 7450 family: a PCI read causes
> the MPC107 to cache the line, and the 7450 to mark the line shared. As
> _PAGE_COHERENT is not set, the 7450 does not produce an address only
> transaction when it writes to the line and changes it back from shared
> to modified. The physical evidence was using the scope to see a PCI read
> go into the MPC107, and the MPC107 respond without any cycles on the 60x
> bus.

Adrian,

I think I understand what you're saying.  The biggest question that comes to
my mind, though, is whether this is a problem on many of the other
hostbridges?  Most of the newer bridges will buffer a cacheline or two.  Is
this a wider issue than just the 107?

Mark


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

  reply	other threads:[~2002-09-10 17:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-09 14:23 Caching in the MPC107 Adrian Cox
2002-09-10 14:58 ` Tom Rini
2002-09-10 15:45   ` Adrian Cox
2002-09-10 17:03     ` Mark A. Greer [this message]
2002-09-10 17:17       ` Adrian Cox
2002-09-10 23:33 ` Paul Mackerras
2002-09-11 12:52   ` Adrian Cox

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=3D7E25F4.4CC00BF8@mvista.com \
    --to=mgreer@mvista.com \
    --cc=adrian@humboldt.co.uk \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.