diff options
| author | David Woodhouse <dwmw2@infradead.org> | 2007-10-13 11:29:07 +0100 |
|---|---|---|
| committer | David Woodhouse <dwmw2@infradead.org> | 2007-10-13 11:29:07 +0100 |
| commit | 85becc535b7f33be5aefdb8ecea9fac4998e4b6f (patch) | |
| tree | b459f5913d6ce3982b8636053f65c0386f6a12b6 /fs/jffs2/build.c | |
| parent | 1437085c3780f064a06df662195a2695e7d75c09 (diff) | |
| download | linux-85becc535b7f33be5aefdb8ecea9fac4998e4b6f.tar.bz2 | |
[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>
Diffstat (limited to 'fs/jffs2/build.c')
| -rw-r--r-- | 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 8c27c12816ba..722a6b682951 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 *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; |