From: Bernhard Priewasser <priewasser@gmail.com>
To: Ferenc Havasi <havasi@inf.u-szeged.hu>,
MTD mailing list <linux-mtd@lists.infradead.org>
Subject: Re: NAND write buffering
Date: Tue, 29 Nov 2005 19:07:38 +0100 [thread overview]
Message-ID: <438C98EA.70105@gmail.com> (raw)
In-Reply-To: <438C94BD.8020300@inf.u-szeged.hu>
Hi all,
I just got the cited mail from Ferenc. I think it is useful for other
people too, that's why it is posted to the list.
Is there anything wrong with our assumptions?
>> JFFS2 is claimed to be powerfail-safe. That's true as far it will
>> _always_ mount, nodes are CRC-protected and scanned at Mount/GC.
>> But what about write buffering on NAND? Doesn't this break lots of the
>> powerfailsafe-efforts? All the data in the writebuffer will be lost.
>> Assuming we are updating a logfile with small data portions. The
>> portions accumulate in wbuf, waiting to reach c->wbuf_pagesize so that
>> the buffer is written to flash. Powerfail: all these small updates can
>> be lost. Hm...
>
> I think you are right. But anyway, if you call "sync" all data will be
> flushed. Unfortunatelly NAND can be written only by page, so the end of
> the wbuf will be filled a padding node. It is a little flash wasting,
> but the data will be written out immediatelly.
>
> Bye,
> Ferenc
Thanks,
Bernhard
next parent reply other threads:[~2005-11-29 18:07 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 ` Bernhard Priewasser [this message]
2005-11-29 19:07 ` NAND write buffering Josh Boyer
2005-11-29 19:12 ` Bernhard Priewasser
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=438C98EA.70105@gmail.com \
--to=priewasser@gmail.com \
--cc=havasi@inf.u-szeged.hu \
--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