From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Ferenc Havasi <havasi@inf.u-szeged.hu>
Cc: Linux MTD <linux-mtd@lists.infradead.org>,
"hinko.kocevar@cetrtapot.si" <hinko.kocevar@cetrtapot.si>
Subject: Re: Great jffs2 speedup
Date: Thu, 29 Sep 2005 11:55:01 +0200 [thread overview]
Message-ID: <20050929095501.GC18741@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <433BB979.7010904@inf.u-szeged.hu>
On Thu, 29 September 2005 11:52:57 +0200, Ferenc Havasi wrote:
> >
> >How is the CS information found during mount? Special location?
>
> There is two way (can be selected via kernel config):
>
> The first way stores a reference in the first (usable) erase block. (If
> it is not free, it moves the data to somewhere else, and reserve). It
> stores only a reference to it at umount, and a "mount-log" at mount
> (just to mark that it is invalid in case of unclean umount). It means
> one page write at mount, one page write at umount. If the erase block
> consist 16 pages than it is necesarry to erase the first erase block
> after every 8 mounts. So the typical timelife of it is about 8*100.000
> mounting, I think it is big enough.
>
> The other way is to specify the cenratlized summary information with
> mount option (not to use the first erase block to store this pointer).
> In this case some other system have to store it (typically on an other
> file system), and the new location after umount can be read using sysfs.
Sounds sane. 100k clean unmounts should be fine for most people. I
know a couple of testers that would immediatly create a simple
while true; do mount mtd0 /mnt -t jffs2; umount /mnt; done
testcase just to prove you wrong, but apart from that...
Jörn
--
To recognize individual spam features you have to try to get into the
mind of the spammer, and frankly I want to spend as little time inside
the minds of spammers as possible.
-- Paul Graham
next prev parent reply other threads:[~2005-09-29 9:55 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 9:36 Great jffs2 speedup hinko.kocevar
2005-09-28 10:00 ` Jörn Engel
2005-09-28 15:26 ` hinko.kocevar
2005-09-29 7:53 ` Jörn Engel
2005-09-30 12:26 ` hinko.kocevar
2005-09-29 8:21 ` Ferenc Havasi
2005-09-29 9:34 ` Jörn Engel
2005-09-29 9:44 ` Artem B. Bityutskiy
2005-09-29 9:52 ` Ferenc Havasi
2005-09-29 9:55 ` Jörn Engel [this message]
2005-09-29 9:59 ` Artem B. Bityutskiy
2005-09-29 10:12 ` Jörn Engel
2005-09-29 10:21 ` Artem B. Bityutskiy
2005-09-29 10:26 ` Jörn Engel
2005-09-29 11:34 ` Ferenc Havasi
2005-09-29 11:35 ` Jörn Engel
2005-09-29 11:45 ` Ferenc Havasi
2005-09-29 11:52 ` Jörn Engel
2005-09-29 12:39 ` Josh Boyer
2005-09-29 10:23 ` Ferenc Havasi
2005-09-29 10:29 ` Jörn Engel
2005-09-29 10:45 ` Artem B. Bityutskiy
2005-09-29 11:29 ` Ferenc Havasi
2005-09-29 11:32 ` Artem B. Bityutskiy
2005-09-29 16:10 ` Peter Grayson
2005-09-29 17:45 ` Sergei Sharonov
2005-09-30 4:19 ` Peter Grayson
2005-09-30 8:58 ` Artem B. Bityutskiy
2005-09-30 9:08 ` Artem B. Bityutskiy
2005-09-30 20:25 ` Peter Grayson
2005-10-01 7:01 ` Artem B. Bityutskiy
2005-09-30 21:15 ` Sergei Sharonov
2005-09-30 23:22 ` Peter Grayson
2005-10-01 7:43 ` Artem B. Bityutskiy
2005-09-29 10:15 ` hinko.kocevar
2005-09-29 12:01 ` Ferenc Havasi
2005-09-29 13:07 ` Jörn Engel
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=20050929095501.GC18741@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=havasi@inf.u-szeged.hu \
--cc=hinko.kocevar@cetrtapot.si \
--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