Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!samsung!mips!pacbell.com!att!linac!midway!quads.uchicago.edu!rtp1
From: rtp1@quads.uchicago.edu (raymond thomas pierrehumbert)
Newsgroups: comp.sys.hp
Subject: Re: A benchmark
Message-ID: <1991May9.155808.8891@midway.uchicago.edu>
Date: 9 May 91 15:58:08 GMT
References: <1991May3.023705.5616@marlin.jcu.edu.au> <5570629@hpfcdc.HP.COM> <1991May9.155313.8671@midway.uchicago.edu>
Sender: news@midway.uchicago.edu (NewsMistress)
Organization: University of Chicago
Lines: 6


Another thing I forgot to mention about IBM's cache architecture.  A
dirty cache line can be stored to memory concurrently with the
load of a new cache line, so in a streaming mode, the bandwidth
to main memory is effectively twice what I mentioned in my previous
post.  I'm curious if HP's cache can do this as well.