000 03729nam a22004935i 4500
001 978-3-031-01724-7
003 DE-He213
005 20240730163652.0
007 cr nn 008mamaa
008 220601s2009 sz | s |||| 0|eng d
020 _a9783031017247
_9978-3-031-01724-7
024 7 _a10.1007/978-3-031-01724-7
_2doi
050 4 _aTK7867-7867.5
072 7 _aTJFC
_2bicssc
072 7 _aTEC008010
_2bisacsh
072 7 _aTJFC
_2thema
082 0 4 _a621.3815
_223
100 1 _aJacob, Bruce.
_eauthor.
_4aut
_4http://id.loc.gov/vocabulary/relators/aut
_979836
245 1 4 _aThe Memory System
_h[electronic resource] :
_bYou Can't Avoid It, You Can't Ignore It, You Can't Fake It /
_cby Bruce Jacob.
250 _a1st ed. 2009.
264 1 _aCham :
_bSpringer International Publishing :
_bImprint: Springer,
_c2009.
300 _aVIII, 69 p.
_bonline resource.
336 _atext
_btxt
_2rdacontent
337 _acomputer
_bc
_2rdamedia
338 _aonline resource
_bcr
_2rdacarrier
347 _atext file
_bPDF
_2rda
490 1 _aSynthesis Lectures on Computer Architecture,
_x1935-3243
505 0 _aPrimers -- It Must Be Modeled Accurately -- ...\ and It Will Change Soon.
520 _aToday, computer-system optimization, at both the hardware and software levels, must consider the details of the memory system in its analysis; failing to do so yields systems that are increasingly inefficient as those systems become more complex. This lecture seeks to introduce the reader to the most important details of the memory system; it targets both computer scientists and computer engineers in industry and in academia. Roughly speaking, computer scientists are the users of the memory system and computer engineers are the designers of the memory system. Both can benefit tremendously from a basic understanding of how the memory system really works: the computer scientist will be better equipped to create algorithms that perform well and the computer engineer will be better equipped to design systems that approach the optimal, given the resource limitations. Currently, there is consensus among architecture researchers that the memory system is "the bottleneck," and this consensus has held for over a decade. Somewhat inexplicably, most of the research in the field is still directed toward improving the CPU to better tolerate a slow memory system, as opposed to addressing the weaknesses of the memory system directly. This lecture should get the bulk of the computer science and computer engineering population up the steep part of the learning curve. Not every CS/CE researcher/developer needs to do work in the memory system, but, just as a carpenter can do his job more efficiently if he knows a little of architecture, and an architect can do his job more efficiently if he knows a little of carpentry, giving the CS/CE worlds better intuition about the memory system should help them build better systems, both software and hardware. Table of Contents: Primers / It Must Be Modeled Accurately / ...\ and It Will Change Soon.
650 0 _aElectronic circuits.
_919581
650 0 _aMicroprocessors.
_979837
650 0 _aComputer architecture.
_93513
650 1 4 _aElectronic Circuits and Systems.
_979838
650 2 4 _aProcessor Architectures.
_979839
710 2 _aSpringerLink (Online service)
_979840
773 0 _tSpringer Nature eBook
776 0 8 _iPrinted edition:
_z9783031005961
776 0 8 _iPrinted edition:
_z9783031028526
830 0 _aSynthesis Lectures on Computer Architecture,
_x1935-3243
_979841
856 4 0 _uhttps://doi.org/10.1007/978-3-031-01724-7
912 _aZDB-2-SXSC
942 _cEBK
999 _c84858
_d84858