home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.windows.x
- Path: sparky!uunet!think.com!paperboy.osf.org!dbrooks
- From: dbrooks@osf.org (David Brooks)
- Subject: Re: FLAME, FLAME ON X!!!
- Message-ID: <1992Nov19.040434.12181@osf.org>
- Followup-To: comp.windows.x
- Sender: news@osf.org (USENET News System)
- Reply-To: dbrooks@osf.org (David Brooks)
- Organization: Open Software Foundation
- References: <RJC.92Nov13144522@daiches.cogsci.ed.ac.uk> <1992Nov16.162457.2923@osf.org> <1ebs7rINNp9k@armory.centerline.com>
- Date: Thu, 19 Nov 1992 04:04:34 GMT
- Lines: 25
-
- jimf@centerline.com (Jim Frost) writes:
-
- >Unfortunately power-of-two allocation is remarkably wasteful of
- >virtual memory (which means wasteful of real live swap space on many
- >systems).
-
- Then why have I heard people recommend using gnu malloc with X, people who
- I thought would be in the know? The only gnu mallocs I've seen use
- exclusively power-of-two allocation, and don't attempt to split a larger
- block or merge blocks on free. There's even a comment:
-
- /* If there are no blocks of the appropriate size, go get some */
- /* COULD SPLIT UP A LARGER BLOCK HERE ... ACT */
-
- > It works fine for very tiny allocations but once you start
- >allocating those "unusual" sizes like 80-byte segments you start
- >seeing major memory waste as well as relatively slow free-element
- >location compared to several other techniques.
-
- Well, maybe X does use relatively small allocations, except for pixmaps
- (which is where we came in).
- --
- David Brooks dbrooks@osf.org
- Open Software Foundation uunet!osf.org!dbrooks
- Allⁿberall und ewig blauen licht die Fernen! Ewig... ewig... earwig... O!
-