Skip to contentSkip to conversation

virtual cache, TLB, and OS

DISCUSSION xu feng 2 participants 2 messages Dec 10, 2006

lore
Share & tools
lore

xu feng

author
#0 lore raw

Hi,

I wish to be personally CC'ed the answers/comments posted to the list in response to this post.

I am confused about the following point regarding Virtual Indexed Tag Indexed Cache and i would appreciate any help

I have read in this article
http://www.linuxjournal.com/article/7105 , the following:
<< In virtually indexed, virtually tagged (VIVT) caches...suffer from several other problems:
1- Virtual address translations usually are changed as part of normal kernel operation, so the cache must pay careful attention to changes in TLB entries (and changes in address space) and flush cache lines whose translations have changed.
2- Even in a single address space, multiple virtual addresses may exist for the same physical address. Each of these virtual addresses would be cached separately, even though they represent the same data. This is called the cache-line aliasing problem.

Quoted 1 line
Quoted 1 line

I am just confused about the author:
1- first point, why the cache has to be bothered by the change in the address logical-physical mapping since it is a virtual cache??

2- could you please give me a situation where two virtual addresses from the same process are mapped to the same physical address?

i can't see this happening since each process page is allocated a dedicated frame.

sorry if my questions seem obvious
thank you for your help

____________________________________________________________________________________
Any questions? Get answers on any topic at www.Answers.yahoo.com. Try it now.

#1 lore raw
Quoted 5 lines · xu feng

I am just confused about the author:
1- first point, why the cache has to be bothered by the change in the address logical-physical mapping since it is a virtual cache??

If you:

1. mmap file A at virtual address X
2. use memory at X
3. mmap file B at X
4. look at X

If its a virtual cache, and it wasn't flushed at step 3, then step 4 will see A's contents rather than B's.

Quoted 7 lines

2- could you please give me a situation where two virtual addresses from the same process are mapped to the same physical address?

i can't see this happening since each process page is allocated a dedicated frame.

If you mmap a file multiple times, then the kernel will assign multiple different virtual addresses for the same page cache page(s).

J