linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: Dave Olien <dmo@osdl.org>
Cc: cliff white <cliffw@osdl.org>,
	mhf@linuxmail.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test8/test9 io scheduler needs tuning?
Date: Wed, 29 Oct 2003 13:40:56 +1100	[thread overview]
Message-ID: <3F9F28B8.9030807@cyberone.com.au> (raw)
In-Reply-To: <20031028211844.GA8285@osdl.org>



Dave Olien wrote:

>Yes, it seems Nick's latest patch from 10/27, has helped reaim
>considerably.
>
>The dbt2 workload still has a problem though.  Mary ran this patch today,
>with deadline and with as-iosched:
>
>2.6.0-test9, elevator=deadline			1644 NOTPM 
>2.6.0-test9, unpatched as-iosched		 977 NOTPM
>2.6.0-test9, as-iosched with as-fix.patch	 980 NOTPM
>
>Higher NOTPM numbers are better.
>

OK, how does 2.6.0-test5 go on these tests?



  reply	other threads:[~2003-10-29  2:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-27 21:52 2.6.0-test8/test9 io scheduler needs tuning? Michael Frank
2003-10-27 22:55 ` cliff white
2003-10-27 23:50   ` Nick Piggin
2003-10-28  1:37     ` Nigel Cunningham
2003-10-28  1:48       ` Nick Piggin
2003-10-28  2:58         ` Michael Frank
2003-10-28  2:57       ` Michael Frank
2003-10-28  3:31       ` Nigel Cunningham
2003-10-28  3:54         ` Nick Piggin
2003-10-28  7:48           ` Michael Frank
2003-10-28  4:13     ` Michael Frank
2003-10-28  4:30       ` Nick Piggin
2003-10-28  6:11         ` Michael Frank
2003-10-28 17:42         ` Martin Josefsson
2003-10-28 17:26     ` cliff white
2003-10-28 21:18       ` Dave Olien
2003-10-29  2:40         ` Nick Piggin [this message]
2003-10-29  4:56           ` Michael Frank
2003-10-29 16:47             ` Michael Frank

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=3F9F28B8.9030807@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=cliffw@osdl.org \
    --cc=dmo@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhf@linuxmail.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;
as well as URLs for NNTP newsgroup(s).