public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Dermot McGahon <dermot@dspsrv.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [RFC] Volatile data device vor jffs2
Date: Wed, 4 Aug 2004 12:04:35 +0200	[thread overview]
Message-ID: <20040804100435.GA10493@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <opsb69q3lv3ertue@mail.dspsrv.com>

On Wed, 4 August 2004 09:55:41 +0100, Dermot McGahon wrote:
> 
> >Comments?
> 
> Well, it still needs to be flushed to something non-volatile at
> some point.

With a DRAM based device, yes.

> You can vary the time between flushes. It depends on how valuable
> that data is to you. With an approach such as this you are really
> deciding how big of a window for data loss you are willing to put
> up with.
> 
> The approach I took while doing this a couple of years ago was not
> to erase blocks until absolutely necessary and then do all the
> garbage collection/file system reorganisation once. This took time
> to do though, was suitable for the device in question (a KVM), but
> possibly not for a general filesystem.

That can be moved to a different thread, as already the case.  Except
for high-throughput write situations, it should be unnoticed by the
user.

Jörn

-- 
The grand essentials of happiness are: something to do, something to
love, and something to hope for.
-- Allan K. Chalmers

      reply	other threads:[~2004-08-04 10:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-31 13:59 [RFC] Volatile data device vor jffs2 Jörn Engel
2004-08-01 12:33 ` David Woodhouse
2004-08-02 17:08   ` Jörn Engel
2004-08-02 17:14     ` Wolfgang Denk
2004-08-02 17:19       ` Jörn Engel
2004-08-04  8:55 ` Dermot McGahon
2004-08-04 10:04   ` Jörn Engel [this message]

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=20040804100435.GA10493@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=dermot@dspsrv.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox