Thread (34 messages) 34 messages, 12 authors, 2004-02-05

Re: Active Memory Defragmentation: Our implementation & problems

From: Dave McCracken <hidden>
Date: 2004-02-05 16:34:24
Also in: lkml

--On Wednesday, February 04, 2004 15:24:57 -0800 Dave Hansen
[off-list ref] wrote:
quoted
Let's say this defragmenter allowed the kernel to detect when 1024 4k 
pages were contiguous and aligned properly and could silently replace 
the processor mapping tables so that all of these "pages" would be 
mapped by one TLB entry.  (At such time that some pages need to get 
freed, the VM would silently switch back to the 4k model.)

This would reduce TLB entries for a lot of programs above a certain 
size, and therefore improve peformance.
This is something that would be interesting to pursue, but we already
have hugetlbfs which does this when you need it explicitly.  When you
know that TLB coverage is a problem, that's your fix for now. 
Hugetlbfs runs from a dedicated pool of large mlocked pages.  This limits
how many hugetlbfs users there can be.

One of the things that's been discussed is letting hugetlbfs use the buddy
allocator in some fashion so it can grow dynamically.  The main barrier to
it is fragmentation, so a working defrag might make it feasible.

Dave McCracken

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help