In message <[EMAIL PROTECTED]>, David Schultz writes: >Thus spake Poul-Henning Kamp <[EMAIL PROTECTED]>: >> >A harder problem to solve is fragmentation for long-running >> >servers, where the RSS tends to creep upwards over time as virtual >> >memory fills with holes. >> >> This is where you want to run phkmalloc with the 'H' option. >> It practically makes it a non-issue last I tried. > >Perhaps phkmalloc could be made self-tuning with regards to 'H'; >I doubt many people know when to use that feature. For example, >you might have a heuristic where phkmalloc detects that the program >has been running for a long time or has called malloc() and free() >many times, so it starts using madvise() on some free pages.
I actually considered adding a "SIGVMMALLOC" which the kernel could use to modify the behaviour of MALLOC to suit present circumstances. Never got around to it before RAM prices dropped. Search the mail-arcives for some of my ideas. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
