Re: memory allocations.

> And you are blaming the runtime.  Fix these program.  There is
> omething wrong if that many allocations are needed.  Ever heard of
> object pools?
> The malloc in glibc 2.3 will have faster locking but this is still no
> excuse for programming like this.

Why does locking come into this. Is glibc not itself keeping per thread
pools to cut down locking overheads ? Is that perhaps something that it
should do rather than g_malloc ?


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]