public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Michael Michael <memmel2@yahoo.com>
To: linux-mtd@lists.infradead.org
Subject: Slow jffs2 startup on DOM
Date: Tue, 19 Feb 2002 22:33:56 -0800 (PST)	[thread overview]
Message-ID: <20020220063356.59191.qmail@web14702.mail.yahoo.com> (raw)
In-Reply-To: <200202191424.g1JEOUk01211@uk-proclin7.altera.com>

Hello I'm using jffs2 on a DOM with the block device
driver. I find the startup times very slow. It seams
to me from reading the source that jffs2 may be
scanning every block with this driver. It takes about
3 min for the first mount. Is there anyway to fix this
?
Would it be  possible to add say a checkpoint such
that if the disk  is "clean" we proceed with normal
startup ?
I do write to the DOM but I can certianly ensure that
its clean except on sudden power downs.  I suspect
that a lot of people who write to the devices can
ensure that the writes are checkpointed so we don't
have to do a full scan.

Mike
 


__________________________________________________
Do You Yahoo!?
Yahoo! Sports - Coverage of the 2002 Olympic Games
http://sports.yahoo.com

  reply	other threads:[~2002-02-20  6:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-19 14:24 jffs2 & new linux zlib Clive Davies
2002-02-20  6:33 ` Michael Michael [this message]
2002-02-20 16:32   ` Slow jffs2 startup on DOM Gad Hayisraeli
2002-02-21  7:35     ` Michael Michael
2002-02-21  8:33     ` David Woodhouse
2002-02-21  9:51       ` Michael Michael
2002-02-21  9:53         ` David Woodhouse
2002-02-21 11:34           ` Michael Michael
2002-02-21 12:32             ` Michael Michael
2002-02-22 12:05             ` Simon Evans
2002-02-22 14:59               ` Michael Michael
2002-02-24  9:18       ` Gad Hayisraeli
2002-02-24 10:47         ` Joakim Tjernlund
2002-02-24 12:04           ` David Woodhouse
     [not found] <14164.1014588644@redhat.com>
2002-02-25  7:47 ` Joakim Tjernlund

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=20020220063356.59191.qmail@web14702.mail.yahoo.com \
    --to=memmel2@yahoo.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