Re: [PATCH 03/12] repair: allocate and free extent records individually

Mark Tinguely
2012-01-12T22:39:46Z

On 01/-10/63 13:59, Christoph Hellwig wrote:
> Instead of allocating inode records in chunks and keeping a freelist of them
> which gets released to the system memory allocator in one go use plain malloc
> and free for them. The freelist just means adding a global lock instead
> of relying on malloc and free which could be implemented lockless. In
> addition smart allocators like tcmalloc have far less overhead than our
> chunk and linked list.

Looks good. Has been running without issues.

Reviewed-by: Mark Tinguely <tinguely@sgi.com>