public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Mike Sullivan <mksully@us.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: I/O degredation with AS on 2.6.0-test3
Date: Tue, 09 Sep 2003 12:44:53 +1000	[thread overview]
Message-ID: <3F5D3EA5.9080900@cyberone.com.au> (raw)
In-Reply-To: <1063052763.29025.100.camel@nighthawk>



Dave Hansen wrote:

>You might want to try Martin Bligh's diffprofile utility.  It's a bit
>hard to compare 2 500-line profiles without it.
>
>ftp://ftp.kernel.org/pub/linux/kernel/people/mbligh/tools/
>
>Also, there have evidently been a few I/O scheduler fixes since -test3. 
>Please retry with -test5.
>

More important, are they regressions vs. previous kernels with AS?



  reply	other threads:[~2003-09-09  2:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-08 18:58 Mike Sullivan
2003-09-08 20:26 ` I/O degredation with AS on 2.6.0-test3 Dave Hansen
2003-09-09  2:44   ` Nick Piggin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-17 15:22 Mike Sullivan
2003-09-17 22:57 ` Nick Piggin

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=3F5D3EA5.9080900@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mksully@us.ibm.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