From: David Woodhouse <dwmw2@infradead.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Pierre Ossman" <drzeus-mmc@drzeus.cx>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
"Jörn Engel" <joern@wohnheim.fh-wedel.de>
Subject: Re: [RFC] MTD driver for MMC cards
Date: Tue, 02 Jan 2007 00:08:40 +0000 [thread overview]
Message-ID: <1167696520.18169.26.camel@shinybook.infradead.org> (raw)
In-Reply-To: <200701012322.14735.arnd@arndb.de>
On Mon, 2007-01-01 at 23:22 +0100, Arnd Bergmann wrote:
> There are multiple efforts in progress to get a jffs2 replacement. NAND
> flash in embedded devices has the same size as it has on MMC card
> potentially, so we will need one soon. David Woodhouse has pushed the
> limit that jffs2 can reasonably used to 512MB, which is the size used
> in the OLPC XO laptop. If there are ways to get beyond that (which I
> find unlikely), there will be a hard limit 2GB or 4GB because of
> limitations in the fs layout.
The main weakness of JFFS2 (at this kind of size) is that there _is_ no
fs layout -- so there isn't a hard 2GiB or 4GiB limit in the format,
because we never encode offsets anywhere but in memory.
We'll push JFFS2 further than the current 512MiB by enlarging the data
nodes -- so each node covers something like 16KiB of data instead of
only 4KiB, and then there'll be about 1/3 as many of them, which will
cut the memory usage and reduce the amount we need to read in the
"summary" blocks. But logfs is the way forward, I agree.
--
dwmw2
next prev parent reply other threads:[~2007-01-02 0:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 13:18 Arnd Bergmann
2006-12-31 12:32 ` Pierre Ossman
2006-12-31 17:40 ` Matthieu CASTET
2007-01-01 22:22 ` Arnd Bergmann
2007-01-02 0:08 ` David Woodhouse [this message]
2007-01-04 7:42 ` Pierre Ossman
2007-04-15 23:33 ` Arnd Bergmann
2007-04-16 0:31 ` 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=1167696520.18169.26.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=arnd@arndb.de \
--cc=drzeus-mmc@drzeus.cx \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®