home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.arch
- Path: sparky!uunet!wupost!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!eff!iWarp.intel.com|ichips!ichips!glew
- From: glew@pdx007.intel.com (Andy Glew)
- Subject: Re: CISC Microcode (was Re: RISC Mainframe)
- In-Reply-To: henry@zoo.toronto.edu's message of Sun, 19 Jul 1992 02:53:25 GMT
- Message-ID: <GLEW.92Jul23184629@pdx007.intel.com>
- Sender: news@ichips.intel.com (News Account)
- Organization: Intel Corp., Hillsboro, Oregon
- References: <9207081402.AA25575@ucbvax.Berkeley.EDU> <GLEW.92Jul12214745@pdx117.intel.com>
- <BrE09F.4JK@metaflow.com> <1992Jul15.163217.434@urbana.mcd.mot.com>
- <BrM813.Du5@zoo.toronto.edu>
- Date: Fri, 24 Jul 1992 02:46:29 GMT
- Lines: 21
-
-
- It's not obvious why you need special instructions for it, however.
- If I recall correctly, the first MIPS chips had the physical address
- space in their kernel virtual space *twice*: the second was uncached,
- specifically so you could do things like bulk data copying without
- trashing the cache.
-
- By the way: creating virtual address aliases with different cache
- properties is a recipe for a complicated, expensive, and lower
- performance than it should be multilevel cache system.
-
- --
-
- Andy Glew, glew@ichips.intel.com
- Intel Corp., M/S JF1-19, 5200 NE Elam Young Pkwy,
- Hillsboro, Oregon 97124-6497
-
- This is a private posting; it does not indicate opinions or positions
- of Intel Corp.
-
- Intel Inside (tm)
-