public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Sergei Sharonov <sergei.sharonov@halliburton.com>
To: linux-mtd@lists.infradead.org
Subject: Re: mounting jffs2
Date: Thu, 21 Apr 2005 15:34:12 +0000 (UTC)	[thread overview]
Message-ID: <loom.20050421T171656-701@post.gmane.org> (raw)
In-Reply-To: 4267B8EF.6000803@inf.u-szeged.hu

Hi,
> Anyway, we are now working on a new boot time speed up technique. We 
> call it centralized summary. The "old" summary is erase block summary.
..................
> If you would like to test it I can send a patch. I would be also useful 
> for us, because we don't have real NAND device, so we cannot make real 
> measurements. (Forutnatelly we can use Artem's NAND simulator.)

Ferenc, I appreciate your help. Unfortunately I don't think the patch will
improve my situation since I need to handle un-clean umounts. e.g. power 
failures and still preserve reasonable mount time.

I did a few tests with yaffs1 and yaffs2. With yaffs1, 128 MByte NAND and 100
MBytes worth of files I am getting 18 s mount time. And after 18 s filesystem
seems to be fully operational (touch, ls -l, etc.) Treat data as 
preliminary since I just built yaffs1 yesterday ;-)
I also did write/read/verify/erase of total of 6.8 GBytes of data without any 
errors. Have not done any power fail testing yet.

Now, the bad news yaffs2 did not work for me - files would disapear or get
corrupted. I would need yaffs2 to handle devices with 2 kB page size.

Sergei Sharonov

      parent reply	other threads:[~2005-04-21 15:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-13 13:25 mounting jffs2 Sergei Sharonov
2005-04-13 13:50 ` Artem B. Bityuckiy
2005-04-13 14:22   ` Sergei Sharonov
2005-04-13 15:02     ` Artem B. Bityuckiy
2005-04-13 17:51       ` Sergei Sharonov
2005-04-14  8:41         ` Artem B. Bityuckiy
2005-04-14 12:39           ` Sergei Sharonov
2005-04-14 13:11             ` Artem B. Bityuckiy
2005-04-14 14:15               ` Sergei Sharonov
2005-04-14 15:18                 ` Artem B. Bityuckiy
2005-04-13 15:18     ` Artem B. Bityuckiy
2005-04-14 20:39   ` Sergei Sharonov
2005-04-14  9:01 ` Ferenc Havasi
2005-04-14  9:15   ` Artem B. Bityuckiy
2005-04-20 14:59     ` Sergei Sharonov
2005-04-20 15:20       ` Artem B. Bityuckiy
2005-04-20 16:34         ` Sergei Sharonov
2005-04-21  7:48       ` Artem B. Bityuckiy
2005-04-21 14:30       ` Ferenc Havasi
2005-04-21 15:31         ` Artem B. Bityuckiy
2005-04-26 13:35           ` Zoltan Sogor
2005-04-26 13:51             ` Artem B. Bityuckiy
2005-04-27  9:39               ` Zoltan Sogor
2005-04-21 15:34         ` Sergei Sharonov [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=loom.20050421T171656-701@post.gmane.org \
    --to=sergei.sharonov@halliburton.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