Article View: comp.os.os2.misc
Article #14766Direct-mapped caches thrash OS/2?
From: Brandon Vanevery
Date: Mon, 04 Jan 1993 06:09
Date: Mon, 04 Jan 1993 06:09
18 lines
1259 bytes
1259 bytes
I'm near to getting a Gateway 486/66-V. Only problem is, their SRAM cache is
direct-mapped. In theory, OS/2 should make the cache thrash during
multi-tasking, thereby making it fairly useless.
In practice, how big a problem is it? If I was only running the OS + 1
memory-intensive number-crunching app, would direct-mapping suffice? i.e.
Does the OS itself count as one of the things you're caching in and out?
Would having a 256K cache, as opposed to 64K, alleviate any problems?
Brandon Van Every
brandon.vanevery@bbs.oit.unc.edu
--
The opinions expressed are not necessarily those of the University of
North Carolina at Chapel Hill, the Campus Office for Information
Technology, or the Experimental Bulletin Board Service.
internet: laUNChpad.unc.edu or 152.2.22.80
Technical Details
Message-ID:
<1993Jan4.060914.7454@samba.oit.unc.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!gatech!concert!samba!usenetShow Full Headers
Complete Article Headers
Newsgroups: comp.os.os2.misc Path: arc1-ca.pugleaf.net!sparky!uunet!gatech!concert!samba!usenet From: Brandon.Vanevery@launchpad.unc.edu (Brandon Vanevery) Subject: Direct-mapped caches thrash OS/2? Message-ID: <1993Jan4.060914.7454@samba.oit.unc.edu> Sender: usenet@samba.oit.unc.edu Nntp-Posting-Host: lambada.oit.unc.edu Organization: University of North Carolina Extended Bulletin Board Service Date: Mon, 4 Jan 1993 06:09:14 GMT Lines: 18