On Thu, Mar 10, 2011 at 12:04 AM, Steven Dake <[email protected]> wrote: > Another interesting idea that may be useful for a second patch is to > keep a list of freed frames to avoid the malloc/free overhead for the > common cases of totemsrp. Surprisingly this is quite a significant > amount of overhead (according to oprofile).
This is definitely good assuming only one thread is going to mess around with the free list. Is that the case here? If you have to add locking, it's even worse. One thing I have done before in that case is create a free list per-thread using thread local storage. -- Russell Bryant _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
