Re: [PATCH 02/12] repair: allocate and free inode records individually

Mark Tinguely
2012-01-12T22:38:52Z

On 01/-10/63 13:59, Christoph Hellwig wrote:
> Instead of allocating inode records in chunks and keeping a freelist of them
> which never gets released to the system memory allocator 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, and the
> freelist is almost completely worthless as we are done allocating new
> inode records once we start freeing them in major quantities.
>

Looks good. Has been running without issues.

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