Home / user-164485

user164485's questions

Martin Hope
user164485
Asked: 2013-03-14 19:29:38 +0800 CST
  • 3

they confuse me.

huge page: the way to manage physical memory of OS kernel, it is split huge page by kernel for reduce the index number in page table.

I get it from : https://stackoverflow.com/questions/1973473/difference-between-cache-and-translation-lookaside-buffertlb

Translation Lookaside Buffer: A Translation lookaside buffer(TLB) is a CPU cache that memory management hardware uses to improve virtual address translation speed.

huge page (OS level) translation Lookaside Buffer(CPU cache)

https://www.kernel.org/doc/Documentation/vm/hugetlbpage.txt the document said , /proc/sys/vm/nr_hugepages indicates the current number of "persistent" huge pages in the kernel's huge page pool.

In my server,

echo 40 > /proc/sys/vm/nr_hugepages   
cat /proc/meminfo | grep -i hugepage   
AnonHugePages:   1675264 kB   
HugePages_Total:      40   
HugePages_Free:       40  
HugePages_Rsvd:        0   
HugePages_Surp:        0   
Hugepagesize:       2048 kB

next, it's my questions.

  1. What's the mean about AnonHugePages ? why is 1675264KB ? I think there are 40 x 2048KB huge page memory. I can't understand.

  2. Why I can't modify Hugepagesize ? in theory, kernel could modify the size. maybe just no the interface in kernel.

  3. How can I get the Translation Lookaside Buffer size? I think system kernel know the size, because the kernel will use it .

I hope I express clearly.
:)

performance