home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.arch
- Path: sparky!uunet!elroy.jpl.nasa.gov!ames!sgi!fido!zola!zuni!tenno.boston.sgi.com!tarolli
- From: tarolli@tenno.boston.sgi.com (Gary Tarolli)
- Subject: Re: CISC Microcode (was Re: RISC Mainframe)
- Message-ID: <nn2q62k@zuni.esd.sgi.com>
- Sender: news@zuni.esd.sgi.com (Net News)
- Organization: Silicon Graphics, Inc.
- References: <9207081402.AA25575@ucbvax.Berkeley.EDU> <32580127@hpcuhe.cup.hp.com> <19920714.070713.843@almaden.ibm.com> <13v76qINN1ap@rodan.UU.NET>
- Date: Fri, 24 Jul 92 18:46:36 GMT
- Lines: 23
-
- In article <13v76qINN1ap@rodan.UU.NET>, avg@rodan.UU.NET (Vadim Antonov) writes:
- |> Did anybody thought that bcopy has nothing to do with the central processor?
- |> I'd prefer to have a machine which thinks of it as of a pair of DMA-s.
- some people think DMA is a dirty word....
-
- |> It makes the whole system more "consistent" from the OS point of view.
- |> There is no need to pump unchanged words through all those CPU
- |> data caches effectively flushing them.
- how do you then keep your data caches consistent with memory (in case some
- of the bcopy's destination bytes were in the cache)? If you flush or invalidate
- your data cache, its not any different than pumping those words thru the cache.
-
- |> The additional circuits are trivial but allow to keep the CPU simplier.
- when one throws in all the non-simple complexities of alignment, direction,
- and sometimes stride (used more for framebuffer operations than memory),
- things become non-trivial real fast. In fact, sometimes, they are complex
- enough that its difficult to ever get DMA working correctly or more efficiently
- than load/stores.
- ______________________________________________________________________________
- _____ ______ _ _ (508)562-4800 tarolli@sgi.com
- / ___ __ __ / __ __ ___ // // * M/S DER-200
- (____/ (_/_/ (_(_/ / (_/_/ (_(_/ (/_(/_/_
- _/
-