public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Peter Grayson <pgrayson@realmsys.com>
To: Sergei Sharonov <sergei.sharonov@halliburton.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Great jffs2 speedup
Date: Fri, 30 Sep 2005 17:22:59 -0600	[thread overview]
Message-ID: <1128122579.6926.110.camel@localhost.localdomain> (raw)
In-Reply-To: <loom.20050930T223859-922@post.gmane.org>

On Fri, 2005-09-30 at 21:15 +0000, Sergei Sharonov wrote:
> Aha!!! Of course, CS reduced your time to first write down to seconds.
> Could you repeat the test after the un-clean unmount (e.g. power off without
> sync)? I bet the numbers will be very different. Probably you also need to 
> be writing to flash during the power off to force full scan on startup.

I'll add this to my list of "things to try for the list".

> Hmm.. I was getting a read throughput jffs2 -> samba network fs of about 
> 1.1 MB/s (180 MHz ARM9, linux 2.6.10, mtd 3/28/2005). I believe jffs2/mtd 
> was the bottleneck since the throughput was 7.25x higher when files were 
> comming from ext2/RAM. Looks like your hw controller is doing a good job.
> Not sure how overhead is split between mtd and jffs2.

The mtd layer does not really introduce any overhead; it accounts for
the time it takes to get bytes in and out of the hardware. Jffs2, on the
other hand, has a number of aspects that use RAM and cpu cycles. Also,
the choices jffs2 makes affects how often it has to access flash.

> Tricky, tricky, tricky ;-)
> Not everybody is that lucky to have a battery. Reminds me of a conversation
> with one "high reliability RTOS" vendor, you guess who.
> - Is your file system power fail safe?
> - Yes, of course. We do require that you use UPS though.
> 
> > However, the thing to
> > remember about centralized summary is that in the unclean shutdown
> > cases, the mount time is no worse than jffs2 without CS. So even if you
> > only expect the filesystem to be cleanly unmounted sometimes, CS can be
> > worth it.
> 
> As long as specification allows for an "occasional" 30 minutes startup time.

Touche.

> Your hw controller does sound very interesting.
> What is the hardware implementation : asic, fpga? Is it available as a 
> separate product (chip)?

This is a soft core in an fpga. My company may be willing to license its
use.

  reply	other threads:[~2005-09-30 23:23 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
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 [this message]
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=1128122579.6926.110.camel@localhost.localdomain \
    --to=pgrayson@realmsys.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=sergei.sharonov@halliburton.com \
    /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