public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Jarkko Lavinen <jlavi@iki.fi>
Cc: MTD List <linux-mtd@lists.infradead.org>, jffs-dev@axis.com
Subject: Re: Benchmarking JFFS2
Date: Tue, 07 May 2002 16:02:06 +0100	[thread overview]
Message-ID: <25024.1020783726@redhat.com> (raw)
In-Reply-To: <20020506151930.A15109@kosh.hut.fi>

jlavi@iki.fi said:
>  I have caught the message 8 times. It doesn't occur rather seldom
> when I have been benchmarking JFFS2 over the weekend.

> On five cases the first line was "Unknown INCOMPAT nodetype C002 at
> 0020293C" (address varies). 

Er, this means it's marked as obsolete on the flash but not in memory. I 
have a vague recollection of having seen this and worked out the cause. 
Is this with the latest code from the jffs2-2_4-branch of CVS? Does it also 
happen with the trunk code?

>  Do you mean kernel profiling? I am using JFFS2 on an Arm based device
> and  kernel profiling is not available for Arm or is it?

Yes. Kernel profiling should work fine on ARM. 

--
dwmw2

  reply	other threads:[~2002-05-07 15:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-02 12:56 Benchmarking JFFS2 Jarkko Lavinen
2002-05-02 13:40 ` David Woodhouse
2002-05-03 17:19   ` Jarkko Lavinen
2002-05-03 17:54     ` David Woodhouse
2002-05-06 12:19       ` Jarkko Lavinen
2002-05-07 15:02         ` David Woodhouse [this message]
2002-05-07 15:13           ` Thomas Gleixner
2002-05-07 17:46           ` Jarkko Lavinen
2002-05-07 19:42             ` David Woodhouse
2002-10-08 17:10         ` David Woodhouse
2002-05-12 19:04   ` David Woodhouse
2002-05-13  8:40     ` Jarkko Lavinen
2002-05-13  9:11       ` David Woodhouse
2002-10-17 10:36   ` Jarkko Lavinen
2003-01-23 12:09     ` David Woodhouse
2003-02-13 12:38       ` Jarkko Lavinen

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=25024.1020783726@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=jffs-dev@axis.com \
    --cc=jlavi@iki.fi \
    --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