Locking kdecore into memory

Reinhold Kainhofer reinhold at kainhofer.com
Tue Jan 23 17:58:27 GMT 2007


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

Am Dienstag, 23. Januar 2007 schrieb Lubos Lunak:
>  Not all of it, just what's used. I think mlockall( MCL_CURRENT ) at a
> suitable place should do. Besides, 30M is hardly a lot with today's 
> machines, 

On my backup machine with 128MB it is a lot! 

Not everyone has the latest-fastest-coolest machine. In fact, kde 3 is running 
nicely on my backup machine. Shall we really go the Vista way and assume the 
user has always the latest hardware?

Cheers,
Reinhold



- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: reinhold at kainhofer.com, http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
 * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFtkzDTqjEwhXvPN0RAhjnAJ9qWKHJHt05SiKE4hmJLr5bXK5aiQCffj9O
l9gWaS3HEZZ+RgNU9v6eHsA=
=lOA9
-----END PGP SIGNATURE-----




More information about the kde-core-devel mailing list