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: Great jffs2 speedup
Date: Thu, 29 Sep 2005 17:45:08 +0000 (UTC)	[thread overview]
Message-ID: <loom.20050929T193349-733@post.gmane.org> (raw)
In-Reply-To: 1128010237.6926.10.camel@localhost.localdomain

Hi,

> CS does, in fact, go a long way toward making 256MB flash parts usable.

Plese define usable. Yes, it does make flash available for read operations
fast but the first time you try to write to it you will be blocked for, I'd
say, anywhere from 5 minutes to a few hours depending on how the files
were written and assuming full 256 MByte filesystem.

> The devices I am building use 256MB, 512MB, and 1024MB nand flash parts.
> We have been using Ferenc's CS patch for some time now and we are able
> to get sub 1 second mount times on 512+ MB filesystems.

Could you please provide time to first write for 256, 512 and 1024 MByte
full filesystems? I presume MB stands for MByte, not Mbit ;-)

> A big part of
> this performance is that I have a nand flash controller that interfaces
> with the nand part on my board. 

Good point.. Can you estimate speedup due to the hw controller?

> But nonetheless, jffs2 can be used
> successfully on very large nand parts. Ferenc's EBS and CS work are
> essential, IMHO, for getting there.

Most embedded systems cannot rely on proper shutdown. So, IMHO CS is of
limited use in this respect.

Sergei Sharonov

  reply	other threads:[~2005-09-29 17:49 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28  9:36 Great jffs2 speedup hinko.kocevar
2005-09-28 10:00 ` Jörn Engel
2005-09-28 15:26   ` hinko.kocevar
2005-09-29  7:53     ` Jörn Engel
2005-09-30 12:26   ` hinko.kocevar
2005-09-29  8:21 ` Ferenc Havasi
2005-09-29  9:34   ` Jörn Engel
2005-09-29  9:44     ` Artem B. Bityutskiy
2005-09-29  9:52     ` Ferenc Havasi
2005-09-29  9:55       ` Jörn Engel
2005-09-29  9:59       ` Artem B. Bityutskiy
2005-09-29 10:12         ` Jörn Engel
2005-09-29 10:21           ` Artem B. Bityutskiy
2005-09-29 10:26             ` Jörn Engel
2005-09-29 11:34               ` Ferenc Havasi
2005-09-29 11:35                 ` Jörn Engel
2005-09-29 11:45                   ` Ferenc Havasi
2005-09-29 11:52                     ` Jörn Engel
2005-09-29 12:39                       ` Josh Boyer
2005-09-29 10:23         ` Ferenc Havasi
2005-09-29 10:29           ` Jörn Engel
2005-09-29 10:45           ` Artem B. Bityutskiy
2005-09-29 11:29             ` Ferenc Havasi
2005-09-29 11:32               ` Artem B. Bityutskiy
2005-09-29 16:10         ` Peter Grayson
2005-09-29 17:45           ` Sergei Sharonov [this message]
2005-09-30  4:19             ` Peter Grayson
2005-09-30  8:58               ` Artem B. Bityutskiy
2005-09-30  9:08                 ` Artem B. Bityutskiy
2005-09-30 20:25                 ` Peter Grayson
2005-10-01  7:01                   ` Artem B. Bityutskiy
2005-09-30 21:15               ` Sergei Sharonov
2005-09-30 23:22                 ` Peter Grayson
2005-10-01  7:43                   ` Artem B. Bityutskiy
2005-09-29 10:15   ` hinko.kocevar
2005-09-29 12:01     ` Ferenc Havasi
2005-09-29 13:07     ` 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=loom.20050929T193349-733@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