From: Jin Xu jinuxst...@gmail.com
In f2fs_write_inode, updating inode after f2fs_balance_fs is not
a optimized way in the case that f2fs_gc is performed ahead. The
inode page will be unnecessarily written out twice, one of which
is in f2fs_gc-...-sync_node_pages and the other
(# of search) = |
`-- (nr_dirty_segments * threshold) /
total_segments,
Otherwise
--
Regards,
Jin
On Thu, Aug 29, 2013 at 8:48 AM, Jin Xu jinuxst...@gmail.com wrote:
From: Jin Xu jinuxst...@gmail.com
This patch improves the foreground
Hi Jaegeuk,
On 04/09/2013 17:40, Jaegeuk Kim wrote:
Hi Jin,
2013-09-04 (수), 07:59 +0800, Jin Xu:
Hi Jaegeuk,
On 03/09/2013 08:45, Jaegeuk Kim wrote:
Hi Jin,
[...]
It seems that we can obtain the performance gain just by setting the
MAX_VICTIM_SEARCH to 4096, for example.
So, how
Hi,
On 11/09/2013 21:19, Kim Jaegeuk wrote:
Hi Russ,
The usage of fs_locks is for the recovery, so it doesn't matter
with stress-testing.
Actually what I've concerned is that we should not grab two or
more fs_locks in the same call path.
Thanks,
I am wondering why we don't use other kind
function call
overhead
- reduce multiplication and division operations
- reduce unnecessary comparison operation
Signed-off-by: Jin Xu jinuxst...@gmail.com
---
fs/f2fs/gc.c | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c
index
Did this patch pass the basic build? There seems have a typo
regarding MAX_BIO_BLOCK.
--
Jin
On 13/09/2013 18:07, Chao Yu wrote:
This patch add macro MAX_BIO_BLOCKS to limit value of npages in
f2fs_bio_alloc,
it can avoid to return NULL in bio_alloc caused by npages is larger than
-dev] [PATCH v2] f2fs: avoid congestion_wait when
do_checkpoint for better performance
Hi Jin,
On 10/10/2013 04:09 PM, Jin Xu wrote:
Hi Gu,
I have a comment below.
Date: Wed, 9 Oct 2013 12:04:09 +0800
From: guz.f...@cn.fujitsu.com
To: yuan.mark.zh...@samsung.com
CC
