Thread (1 message) 1 message, 1 author, 2000-06-06

Re: memory pressure callbacks (was: 2.5 TODO)

From: Stephen C. Tweedie <hidden>
Date: 2000-06-06 20:12:32

Hi,

On Tue, Jun 06, 2000 at 01:06:00PM -0700, Chris Mason wrote:
quoted
Chris, I think that you don't want to put that in the address space
operations, the main reason is that you don't want your pages to stay
in the main LRU queue, because you need to freed them in an specific
order (not LRU at all).  Then if shrink_mmap is not scanning your
pages, it is better to use your own reclaim function, that would be
called from do_try_to_free_pages (a la shrink_[di]cache way).
The goal isn't to make something perfect for the journaled filesystems, it
is a generic facility that also happens to work for the journaled
filesystems.  So, I like the address space operations, mostly
because this is an operation on an address space ;-)
Right.  There's one other major problem with a lot of page reclaim 
algorithms --- the algorithm can be the best in the world, but it needs
to be balanced against the other page stealers in the kernel too. 
Using the main LRUs for all filesystems, with address_space callbacks
to free pages, should make such balancing a lot easier to achieve.

Cheers,
 Stephen
--
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.eu.org/Linux-MM/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help