Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Edwin Eyan Moragas (eyanyndy.org)
Date: Sat Aug 07 2010 - 20:36:44 CDT
On Sun, Aug 8, 2010 at 4:19 AM, Kenneth Gober <kgobergmail.com> wrote:
> On Sat, Aug 7, 2010 at 4:03 PM, Henning Brauer
>> * Ted Unangst <ted.unangstgmail.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
> a far better solution. modifying your app to use malloc(3) and free(3)
> conservatively may be a viable option as well, although at that point
came across this several times. thank you. i guess this is the way.
just lessen calls to malloc and free? but isn't this just a
was wondering if there are any special 'moves' that are employed in
creating daemons in openbsd that the devs might care to share.
> starting down the road of writing your own allocator again.