From: Bernhard Priewasser <priewasser@gmail.com>
To: Josh Boyer <jwboyer@gmail.com>
Cc: MTD mailing list <linux-mtd@lists.infradead.org>
Subject: Re: NAND write buffering
Date: Tue, 29 Nov 2005 20:12:47 +0100 [thread overview]
Message-ID: <438CA82F.50600@gmail.com> (raw)
In-Reply-To: <625fc13d0511291107t3495a41byae11ba1832657291@mail.gmail.com>
> The assumptions seem to be fine. The usage case you described is
> probably the worst case for JFFS2 though. Lots of small writes
> generates lots of data nodes, which in turn increases mount time and
> wastes space. EBS helps with the mount time issue, but the flash
> space consumption is larger than it probably needs to be. But as you
> correctly pointed out, there is nothing you can do about that if you
> _must_ have it be on flash after every write.
Hehe... I'd say: rather use the flash unefficiently (sizeof(header) >>
sizueof(data)) than loose data!
Bernhard
next prev parent reply other threads:[~2005-11-29 19:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <438C7B0C.5040001@gmail.com>
[not found] ` <438C94BD.8020300@inf.u-szeged.hu>
2005-11-29 18:07 ` NAND write buffering Bernhard Priewasser
2005-11-29 19:07 ` Josh Boyer
2005-11-29 19:12 ` Bernhard Priewasser [this message]
2005-11-30 9:08 ` Jörn Engel
2005-12-12 14:39 ` Bernhard Priewasser
2005-12-12 15:37 ` Josh Boyer
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=438CA82F.50600@gmail.com \
--to=priewasser@gmail.com \
--cc=jwboyer@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.