From: David Woodhouse <dwmw2@infradead.org>
To: Matthieu CASTET <matthieu.castet@parrot.fr>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2 Erase Block Summary overhead
Date: Mon, 19 Feb 2007 10:05:37 +0000 [thread overview]
Message-ID: <1171879537.7600.5.camel@pmac.infradead.org> (raw)
In-Reply-To: <45D47C92.8080908@parrot.fr>
On Thu, 2007-02-15 at 16:30 +0100, Matthieu CASTET wrote:
> after doing some test on a 64MB nand flash, we see that only 50 MB can
> be stored on the filesystem [1]. The extra 10 MB are taken by jffs2 summary.
> If we disable jffs2 sumary in the kernel, the 10MB become available.
>
> Is there a way to reduce this overhead ?
> 20 % seems really big.
There's a lot of redundant information in the summary; I think we could
halve it fairly easily. I don't believe your 20% figure though -- that's
too high. You really can't rely on the output of df.
--
dwmw2
next prev parent reply other threads:[~2007-02-19 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 15:30 jffs2 Erase Block Summary overhead Matthieu CASTET
2007-02-19 10:05 ` David Woodhouse [this message]
2007-02-19 10:58 ` Matthieu CASTET
2007-02-19 11:15 ` Matthieu CASTET
2007-02-19 11:10 ` Indrek Kruusa
2007-02-20 8:45 ` Matthieu CASTET
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=1171879537.7600.5.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=matthieu.castet@parrot.fr \
/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