Commit:     85becc535b7f33be5aefdb8ecea9fac4998e4b6f
Parent:     1437085c3780f064a06df662195a2695e7d75c09
Author:     David Woodhouse <[EMAIL PROTECTED]>
AuthorDate: Sat Oct 13 11:29:07 2007 +0100
Committer:  David Woodhouse <[EMAIL PROTECTED]>
CommitDate: Sat Oct 13 11:29:07 2007 +0100

    [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 <[EMAIL PROTECTED]>
 fs/jffs2/build.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/fs/jffs2/build.c b/fs/jffs2/build.c
index 8c27c12..722a6b6 100644
--- a/fs/jffs2/build.c
+++ b/fs/jffs2/build.c
@@ -289,7 +289,7 @@ static void jffs2_calc_trigger_levels(struct jffs2_sb_info 
           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;
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at

Reply via email to