Date: Wed, 23 Oct 2002 21:34:52 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: David Schultz <dschultz@uclink.Berkeley.EDU> Cc: Danny Braniss <danny@cs.huji.ac.il>, freebsd-hackers@FreeBSD.ORG Subject: Re: malloc Message-ID: <45228.1035401692@critter.freebsd.dk> In-Reply-To: Your message of "Wed, 23 Oct 2002 12:13:56 PDT." <20021023191355.GA728@HAL9000.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20021023191355.GA728@HAL9000.homeunix.com>, David Schultz writes: >Thus spake Poul-Henning Kamp <phk@critter.freebsd.dk>: >> >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 phk@FreeBSD.ORG | 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 majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45228.1035401692>