|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: memory fragmentation
From: Kenneth Gober (kgober
gmail.com)
Date: Sat Aug 07 2010 - 15:19:38 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Aug 7, 2010 at 4:03 PM, Henning Brauer <lists-openbsd
bsws.de>wrote:
> * Ted Unangst <ted.unangst
gmail.com> [2010-08-07 19:54]:
> > you write your own allocator.
>
> don't. ever.
to put it another way, if memory fragmentation ever does become a problem
for you, there is probably an easier and safer solution than writing your
own allocator. upgrading to a 64-bit platform, for example, is likely to be
a far better solution. modifying your app to use malloc(3) and free(3) more
conservatively may be a viable option as well, although at that point you're
starting down the road of writing your own allocator again.
-ken
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]