un...@huawei.com]
> Sent: Tuesday, December 29, 2015 7:11 PM
> To: Jaegeuk Kim
> Cc: linux-fsde...@vger.kernel.org; linux-kernel@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net
> Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: use atomic variable for
> total_extent_tree
>
>
On 2015/12/22 11:38, Jaegeuk Kim wrote:
It would be better to use atomic variable for total_extent_tree.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/debug.c| 5 +++--
fs/f2fs/extent_cache.c | 8
fs/f2fs/f2fs.h | 2 +-
fs/f2fs/node.c | 3 ++-
fs/f2fs/shrinker.c
22, 2015 11:39 AM
> > > To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org;
> > > linux-f2fs-de...@lists.sourceforge.net
> > > Cc: Jaegeuk Kim
> > > Subject: [f2fs-dev] [PATCH 1/2] f2fs: use atomic variable for
> > > total_extent_tree
>
.kernel.org;
> > linux-f2fs-de...@lists.sourceforge.net
> > Cc: Jaegeuk Kim
> > Subject: [f2fs-dev] [PATCH 1/2] f2fs: use atomic variable for
> > total_extent_tree
> >
> > It would be better to use atomic variable for total_extent_tree.
>
> total_extent_tree was pr
dev] [PATCH 1/2] f2fs: use atomic variable for
> total_extent_tree
>
> It would be better to use atomic variable for total_extent_tree.
total_extent_tree was protected by extent_tree_lock semaphore, so intention here
is to make related calculation in available_free_memory or update_gener
It would be better to use atomic variable for total_extent_tree.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/debug.c| 5 +++--
fs/f2fs/extent_cache.c | 8
fs/f2fs/f2fs.h | 2 +-
fs/f2fs/node.c | 3 ++-
fs/f2fs/shrinker.c | 3 ++-
5 files changed, 12 insertions(+),
6 matches
Mail list logo
