Navi

Cache

Good Day to everyone =)

For this post is only discuss about the Cache. So that will not be so long post for your guys to reading =)

What is Cache?
Everyone only know the words of "Cache" or heard it before, but they might be do not know what is meant of the Cache and how it working inside the computer.

For today, i want to explain to your guys the "Cache",how it working and also the structure of cache and main memory :)


Cache is a small amount of fast memory. It is located and intermediate buffer between the CPU (Control Process Unit) and the normal Main Memory. Furthermore, cache is contain a copy of portions of main memory.


























Cache Read Operation






Generate the RA(Reference Address) of word to be read.
Check if the word is inside the cache.
-If it is, deliver the word to processor.( Known as Cache Hit, it's fast)
-If not, block of main memory read into cache.( Known as Cache Miss, it's slow)
Locality of reference principle applies
-Future references likely to other words in block read into cache. 
















Typically Cache Organization



Cache Structure & Main Memory Structure





















In addition
that's no matter for the size of the cache.
But the more cache require, then that's more expensive.
Of course, the speed of cache is same as car engine.
More powerful car engine, the speed more faster.
More cache inside process, the speed also more faster
Last but not least, the larger cache has a larger gates involve-slow down
and take more time to check the data.


Well...  
I think your guys should gain some new information of cache 
after viewed my posted, right? xD

But remember that, "One is never too old to learn". 
For more information of cache, 
you may go to search it from the wiki-pedia or google by yourself. =)
Anyway,thanks for reading my posted. 
Have a nice day ! see ya~~







                                                                                                                                           Written by--®æŋ





















0 comments: