[JFFS2] Relax threshold for triggering GC due to dirty blocks.

Instead of matching resv_blocks_gcmerge, which is only about 3, instead
match resv_blocks_gctrigger, which includes a proportion of the total
device size.

These ought to become tunable from userspace, at some point.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>

diff --git a/fs/jffs2/build.c b/fs/jffs2/build.c
index 8c27c12816ba4ea131d4d7deb78b828a59fd9b4d..722a6b682951b8bcdecac8107171c2d06f5d60be 100644 (file)
--- a/fs/jffs2/build.c
+++ b/fs/jffs2/build.c
@@ -289,7 +289,7 @@ static void jffs2_calc_trigger_levels(struct jffs2_sb_info *c)
           trigger the GC thread even if we don't _need_ the space. When we
           can't mark nodes obsolete on the medium, the old dirty nodes cause
           performance problems because we have to inspect and discard them. */
-       c->vdirty_blocks_gctrigger = c->resv_blocks_gcmerge;
+       c->vdirty_blocks_gctrigger = c->resv_blocks_gctrigger;
        if (jffs2_can_mark_obsolete(c))
                c->vdirty_blocks_gctrigger *= 10;