From: David Woodhouse <dwmw2@infradead.org>
To: "Koenders, Eric - NL" <Eric.Koenders@peekglobal.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: System blocked for a while by heavily fragmented file on a jffs2 partition
Date: Tue, 21 Dec 2004 11:37:37 +0000 [thread overview]
Message-ID: <1103629058.6111.53.camel@localhost.localdomain> (raw)
In-Reply-To: <ECE7E5A7BCD66544A8F2B98EA0A8EFB313E239@nlsv0101.nl.peeknet.prv>
On Thu, 2004-12-09 at 17:17 +0100, Koenders, Eric - NL wrote:
> Does anyone have an idea how to solve this problem? Maybe more agressive
> defragmentation behaviour of the GC? Or an fsck like tool to defragment a
> file system?
It would help to concentrate harder on garbage-collecting the files with
tiny nodes. Currently we do keep track of whether a node is an optimal
representation ('REF_PRISTINE') or not, but we only use that when we're
_actually_ garbage collecting; we don't use it to decide which blocks to
GC.
Also, the oft-suggested optimisation of writing new nodes out to a
_separate_ block from GC-rewritten nodes would probably help to improve
the GC performance here.
--
dwmw2
prev parent reply other threads:[~2004-12-21 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 16:17 System blocked for a while by heavily fragmented file on a jffs2 partition Koenders, Eric - NL
2004-12-21 11:37 ` David Woodhouse [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1103629058.6111.53.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=Eric.Koenders@peekglobal.com \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox