Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

About Memory Hierarchy Issue

Status
Not open for further replies.

javatea

Newbie level 4
Joined
Dec 6, 2009
Messages
6
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Activity points
1,326
Hi Folks,

In practice, we used register file, sram, dram as our storage devices for implementation of memory hierarchy. The capacity and performance (memory access speed ) is always a trade off.
I were asked a question. "why not use SRAM to build L1, L2 and L3? SRAM is faster than DRAM, maybe we could use many SRAMs to build a DRAM." Is it possible/feasible?
I know cost is an issue in this question.
Any other issues could explain why not build SRAM everywhere in our memory hierarchy?
e.g.
L1 : SRAM
L2 : many many SRAMs
Thank you.
 

This question is just a 'catch' to check if you know what is Cache.

Cache is actually SRAM. The difference that we can say is that it is on-chip with processor i.e. on-chip-SRAM is cache.
 

Thank you.
But my question is
If SRAM is faster, why not use SRAM to build everywhere?
 

Besides cost you need to think about power and space.

SRAM has a lower density than DRAM.
It is also more power hungry as compared to DRAM.

Vice versa for cache!
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top