Article View: comp.arch
Article #10718Re: Vector vs Cache/Superscalar
From: raymond thomas pierrehumbert
Date: Wed, 08 May 1991 15:54
Date: Wed, 08 May 1991 15:54
16 lines
1263 bytes
1263 bytes
Andrew Glew, of Intel, writes > So: why not combine vector memory access instructions that convey >access pattern, with scalar computational operations? Yes, yes, my point exactly. Please do it! I'll take 10. In fact, I think a fruitful area for extending the current architectures is in a more general model for pre-loading the cache. Doing pre-loads by constant strides rather than by contiguous lines would already be a big performance boost, but I could also imagine more general solutions, where you gave the memory subsystem a vector of addresses which specified the pre-load pattern. I'm just a user though. I'm not at all clear how hard these things would be to implement in hardware. .
Technical Details
Message-ID:
<1991May8.155455.14491@midway.uchicago.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!linac!midway!quads.uchicago.edu!rtp1References:
<1991May6.035310.26794@marlin.jcu.edu.au> <11921@mentor.cc.purdue.edu> <GLEW.91May7172546@pdx007.intel.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!linac!midway!quads.uchicago.edu!rtp1 From: rtp1@quads.uchicago.edu (raymond thomas pierrehumbert) Newsgroups: comp.arch Subject: Re: Vector vs Cache/Superscalar Message-ID: <1991May8.155455.14491@midway.uchicago.edu> Date: 8 May 91 15:54:55 GMT References: <1991May6.035310.26794@marlin.jcu.edu.au> <11921@mentor.cc.purdue.edu> <GLEW.91May7172546@pdx007.intel.com> Sender: news@midway.uchicago.edu (NewsMistress) Organization: University of Chicago Lines: 16