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: Fri, 03 May 2002 18:54:34 +0100	[thread overview]
Message-ID: <28528.1020448474@redhat.com> (raw)
In-Reply-To: <20020503201900.A32761@kosh.hut.fi>

jlavi@iki.fi said:
>  During my benchmark runs I have encountered 'Eep. read_inode() failed
> for  ino #...'. Is this something I should be concerned?

Er, yes, that is concerning. Does it say why? If it's only occasional, then 
it's almost certainly memory allocation problems. 

It would be useful if you could provide a profiling run from the
worst-performing case, so we can see where it's spending the time. I've 
already voiced my suspicions, but I've been wrong before; I only wrote it :)

--
dwmw2

  reply	other threads:[~2002-05-03 17:55 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 [this message]
2002-05-06 12:19       ` Jarkko Lavinen
2002-05-07 15:02         ` David Woodhouse
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=28528.1020448474@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