From: David Woodhouse <dwmw2@infradead.org>
To: "Curtis, Allen" <Allen.Curtis@Thales-IFS.com>
Cc: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: jffs2_scan_eraseblock() - errors
Date: Wed, 31 Jul 2002 04:07:45 +0100 [thread overview]
Message-ID: <20909.1028084865@redhat.com> (raw)
In-Reply-To: <FA06AA2C99BCD511951200005A99441001E3ECC9@irvexch1.sextantifs.com>
Allen.Curtis@Thales-IFS.com said:
> INOCACHE_HASHSIZE was set to 1. Changed this to 128 and....
> real 47.258s sys 47.25s
Hmm. Out of interest, What happens if you apply this? Again, profile data
are useful :)
DO NOT LEAVE THIS IN. It disables the CRC32 check on nodes during mount.
It's the first (and easy) part of the proof-of-concept which involves
moving said CRC32 check to later so the mount doesn't have to wait for it.
Index: scan.c
===================================================================
RCS file: /home/cvs/mtd/fs/jffs2/scan.c,v
retrieving revision 1.51.2.3
diff -u -p -r1.51.2.3 scan.c
--- scan.c 25 Jul 2002 20:49:06 -0000 1.51.2.3
+++ scan.c 31 Jul 2002 03:06:44 -0000
@@ -467,7 +467,7 @@ static int jffs2_scan_inode_node(struct
ri.csize = 0;
}
- if (ri.csize) {
+ if (0 && ri.csize) {
/* Check data CRC too */
unsigned char *dbuf;
__u32 crc;
--
dwmw2
next prev parent reply other threads:[~2002-07-31 3:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 1:15 jffs2_scan_eraseblock() - errors Curtis, Allen
2002-07-31 3:07 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-31 23:02 Curtis, Allen
2002-08-01 10:44 ` David Woodhouse
2002-07-31 0:38 Curtis, Allen
2002-07-31 0:48 ` David Woodhouse
2002-07-30 23:59 Curtis, Allen
2002-07-31 0:15 ` David Woodhouse
2002-07-31 0:18 ` David Woodhouse
2002-07-30 23:30 Curtis, Allen
2002-07-30 23:42 ` David Woodhouse
2002-07-30 18:11 Curtis, Allen
2002-07-30 22:21 ` David Woodhouse
2002-07-31 10:34 ` Jörn Engel
2002-07-31 11:45 ` David Woodhouse
2002-07-31 11:57 ` Jörn Engel
2002-07-31 11:59 ` David Woodhouse
2002-07-31 12:16 ` Jörn Engel
2002-07-31 12:17 ` David Woodhouse
2002-07-31 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=20909.1028084865@redhat.com \
--to=dwmw2@infradead.org \
--cc=Allen.Curtis@Thales-IFS.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.