[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:       Thomas Zander <zander () planescape ! com>
Date:       2002-07-28 14:15:07
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 27 July 2002 02:04, Ryan Cumming wrote:
> 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.

Last I heard file buffers are still the first to go when memory is needed. 
Even well before swapping (data OR code) is done in the first place. Did you 
misunderstand Werner, or what?

- -- 
Thomas Zander                                           zander@planescape.com
                                                 We are what we pretend to be
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9Q/xrCojCW6H2z/QRAo9uAJ0ZET2/E+OPqLIU05bx8JcNfj3blQCgtbAo
d20eUWKeeFdHh/MzfSUa/Cw=
=MRcq
-----END PGP SIGNATURE-----

_______________________________________________
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]