From: David Woodhouse <dwmw2@infradead.org>
To: "Joakim Tjernlund" <Joakim.Tjernlund@lumentis.se>
Cc: linux-mtd@lists.infradead.org, jffs-dev@axis.com
Subject: Re: CLEANMARKER question
Date: Sat, 05 Jan 2002 12:59:31 +0000 [thread overview]
Message-ID: <6691.1010235571@redhat.com> (raw)
In-Reply-To: <001001c195e3$cd5fb180$5a9240d5@jocke>
Joakim.Tjernlund@lumentis.se said:
> I have seen alot of posts about it but I have no idea on how to
> proceed with this.
The basic idea is to make it nice and quick for the FS code to reproduce
its internal data (the jffs2_raw_node_ref lists and clean/dirty sizes) on
mount without having to work it all out from scratch. Look at what the
mount code does, and see how much could be avoided - then work out
precisely what needs to go into the checkpoint - it'll probably end up
being a tradeoff between remount speed and the size taken by the checkpoint
nodes.
I wonder if we could get away with writing a node at the _end_ of each
eraseblock, just listing the start addresses of the nodes contained within
that block?
> Would checkpointing still speed up mount when power is cut and then
> restored?
If you write a checkpoint only on a clean unmount, then no.
If you do it periodically during normal operation. then yes.
--
dwmw2
next prev parent reply other threads:[~2002-01-05 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-05 12:23 CLEANMARKER question Joakim Tjernlund
2002-01-05 12:59 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-12 12:14 Cache mappings and invalidate Joakim Tjernlund
2002-01-04 8:59 ` CLEANMARKER question Joakim Tjernlund
2002-01-04 9:42 ` David Woodhouse
2002-01-04 10:33 ` Joakim Tjernlund
2002-01-04 10:41 ` David Woodhouse
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=6691.1010235571@redhat.com \
--to=dwmw2@infradead.org \
--cc=Joakim.Tjernlund@lumentis.se \
--cc=jffs-dev@axis.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