Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
lru
1 view
Skip to first unread message
EECS Instructional Account
Aug 10, 2008, 3:21:23 PM8/10/08
to
whats wrong with implementing an lru algorithm where the block just read
or write gets a lru.value = 0 (most recent accessed)and then I add 1 to
each OTHER VALID block's lru.value. Theoretically, two blocks should never
have the same value in between calls to accessMemory right? The reason I
ask is that Albert mentioned that we probably should change init_lru,
which zeroes out lru.value's
or write gets a lru.value = 0 (most recent accessed)and then I add 1 to
each OTHER VALID block's lru.value. Theoretically, two blocks should never
have the same value in between calls to accessMemory right? The reason I
ask is that Albert mentioned that we probably should change init_lru,
which zeroes out lru.value's
[Instr] Albert Chae
Aug 10, 2008, 4:39:17 PM8/10/08
to
Who said there was anything wrong with that... I just meant that you
should change init_lru depending on your representation of LRU.
should change init_lru depending on your representation of LRU.
Albert
0 new messages