All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: Gabriel Paubert <paubert@iram.es>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: PATCH: improved processor config for G3s
Date: Tue, 5 Sep 2000 12:50:25 +0200	[thread overview]
Message-ID: <20000905105025.300@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.HPX.4.10.10009041309060.15438-100000@gra-ux1.iram.es>


>
>The absence of broadcast might definitely harm, but first the support for
>store gathering in the MPC106 (Grackle) is quite poor:
>
>"For a stream of single-beat writes, the data for the first transaction is
>latched in the first buffer and the MPC106 initiates the transaction on
>the PCI bus. The second single-beat write is then stored in the second
>buffer. For subsequent single-beat writes, store gathering is possible if
>the incoming write is to sequential bytes in the same half cache line as
>the previously latched data. Store gathering is only used for writes to
>PCI memory space, not for writes to PCI I/O space. The store gathering
>continues until the buffer is scheduled to be flushed or until the
>processor issues a synchronizing transaction.

Well, that would help unaccelerated frame buffers (but are there any on
Grackle-based machines ?)


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

  reply	other threads:[~2000-09-05 10:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-03 13:03 PATCH: improved processor config for G3s Michel Lanners
2000-09-03 13:43 ` Benjamin Herrenschmidt
2000-09-04  9:48   ` Gabriel Paubert
2000-09-04 10:34     ` Adrian Cox
2000-09-04 10:54       ` Benjamin Herrenschmidt
2000-09-05  9:49         ` Gabriel Paubert
2000-09-05 10:50           ` Benjamin Herrenschmidt [this message]
2000-09-05 11:06             ` Gabriel Paubert
2000-09-05 11:32           ` Adrian Cox
2000-09-04 17:51     ` Michel Lanners

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=20000905105025.300@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paubert@iram.es \
    /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.