linux-kernel - Re: [PATCH 3/3] f2fs: enhnace alloc_nid and build_free

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKYAXd_f8Vqd=zrUf0PpccuJFtUF5rW-74wt4oac2M0etT5YVA@mail.gmail.com>
Date:	Fri, 26 Apr 2013 10:44:03 +0900
From:	Namjae Jeon <linkinjeon@...il.com>
To:	Jaegeuk Kim <jaegeuk.kim@...sung.com>
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-f2fs-devel@...ts.sourceforge.net
Subject: Re: [PATCH 3/3] f2fs: enhnace alloc_nid and build_free_nids flows

2013/4/25, Jaegeuk Kim <jaegeuk.kim@...sung.com>:
> 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@...sung.com>
I can't find any issues in this patch.
Reviewed-by: Namjae Jeon <namjae.jeon@...sung.com>

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