public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: linux-os@analogic.com
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Low file-system performance for 2.6.11 compared to 2.4.26
Date: Fri, 01 Apr 2005 10:13:11 +1000	[thread overview]
Message-ID: <424C9217.9000205@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.61.0503311129360.4710@chaos.analogic.com>

linux-os wrote:
> 
> For those interested, some file-system tests and a test-tools
> are attached.
> 

I'll give it a run when I get a chance. Thanks.
In the meantime, can you try with different io schedulers?

> Also, my .signature disappeared during the file-system tests.
> There were no errors and e2fsck thinks everything is fine!
> 

You seem to be constantly plagued by gremlins. I don't
know whether to laugh or cry.


  parent reply	other threads:[~2005-04-01  0:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-31 16:34 Low file-system performance for 2.6.11 compared to 2.4.26 linux-os
2005-03-31 23:59 ` Lincoln Dale
2005-04-01  0:13 ` Nick Piggin [this message]
2005-04-01 18:13   ` Richard B. Johnson

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=424C9217.9000205@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.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