Re: [PATCH 3/3] f2fs: enhnace alloc_nid and build_free_nids flows

[Namjae Jeon]

2013/4/25, Jaegeuk Kim <jaegeuk.kim@xxxxxxxxxxx>:
> In order to avoid build_free_nid lock contention, let's change the order of
> function calls as follows.
>
> At first, check whether there is enough free nids.
>  - If available, just get a free nid with spin_lock without any overhead.
>  - Otherwise, conduct build_free_nids.
>   : scan nat pages, journal nat entries, and nat cache entries.
>
> We should consider carefullly not to serve free nids intermediately made by
> build_free_nids.
> We can get stable free nids only after build_free_nids is done.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk.kim@xxxxxxxxxxx>
I can't find any issues in this patch.
Reviewed-by: Namjae Jeon <namjae.jeon@xxxxxxxxxxx>

Thanks.
> ---
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/