[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: Fwd: [PATCH] Limit KoPicture's memory usage
From:       Ryan Cumming <ryan () completely ! kicks-ass ! org>
Date:       2002-07-27 0:04:34
[Download RAW message or body]

On July 26, 2002 06:01, Werner Trobin wrote:
> The idea behind that is to use a file for storing the data, as files have
> less priority than, say, code pages, and so the bitmaps would get mapped
> out before something "important" gets mapped out.

That is simply not true under Linux. Code pages are just memory mapped files, 
and the kernel does not view them any differently from any other memory 
mapped file. Even if non-code file backed mappings got paged out 
preferentially over code pages, what's the point? The kernel will only page 
out the code pages first if they're being used -less often- than the data 
file. In which case, it really should've been paged out first, no?

The VM allocator sounds like a needless hack to me.

-Ryan
_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]