All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.61-mm1
Date: Sat, 15 Feb 2003 18:25:38 +1100	[thread overview]
Message-ID: <3E4DEB72.4010405@cyberone.com.au> (raw)
In-Reply-To: 20030214231356.59e2ef51.akpm@digeo.com

Andrew Morton wrote:

>http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.61/2.5.61-mm1/
>
>. Jens has fixed the request queue aliasing problem and we are no longer
>  able to break the IO scheduler.  This was preventing the OSDL team from
>  running dbt2 against recent kernels, so hopefully that is all fixed up now.
>
>. The anticipatory scheduler is performing well.  I've included that now.
>
And for those interested, if you find unusual IO performance,
please try disabling AS and reporting results. Thanks.

echo 0 > /sys/block/?/iosched/antic_expire

This value defaults to 10 (ms). More than around 20 might do
funny though not harmful stuff due to a fragile bitshift.

Nick



WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <piggin@cyberone.com.au>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.61-mm1
Date: Sat, 15 Feb 2003 18:25:38 +1100	[thread overview]
Message-ID: <3E4DEB72.4010405@cyberone.com.au> (raw)
In-Reply-To: 20030214231356.59e2ef51.akpm@digeo.com

Andrew Morton wrote:

>http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.61/2.5.61-mm1/
>
>. Jens has fixed the request queue aliasing problem and we are no longer
>  able to break the IO scheduler.  This was preventing the OSDL team from
>  running dbt2 against recent kernels, so hopefully that is all fixed up now.
>
>. The anticipatory scheduler is performing well.  I've included that now.
>
And for those interested, if you find unusual IO performance,
please try disabling AS and reporting results. Thanks.

echo 0 > /sys/block/?/iosched/antic_expire

This value defaults to 10 (ms). More than around 20 might do
funny though not harmful stuff due to a fragile bitshift.

Nick


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>

  reply	other threads:[~2003-02-15  7:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-15  7:13 2.5.61-mm1 Andrew Morton
2003-02-15  7:13 ` 2.5.61-mm1 Andrew Morton
2003-02-15  7:25 ` Nick Piggin [this message]
2003-02-15  7:25   ` 2.5.61-mm1 Nick Piggin
2003-02-15 11:27 ` 2.5.61-mm1 Con Kolivas
2003-02-15 23:41   ` 2.5.61-mm1 Andrew Morton
2003-02-16  1:03     ` 2.5.61-mm1 Con Kolivas
2003-02-15 14:29 ` 2.5.61-mm1 Ed Tomlinson
2003-02-15 14:29   ` 2.5.61-mm1 Ed Tomlinson
2003-02-16  0:12 ` 2.5.61-mm1 James H. Cloos Jr.
2003-02-16  0:29   ` 2.5.61-mm1 Andrew Morton
2003-02-17 11:38     ` 2.5.61-mm1 Maneesh Soni
2003-02-17 11:29       ` 2.5.61-mm1 Andrew Morton
2003-02-17 22:44 ` 2.5.61-mm1 Cliff White
2003-02-17 22:44   ` 2.5.61-mm1 Cliff White
  -- strict thread matches above, loose matches on Subject: below --
2003-02-17 22:50 2.5.61-mm1 Cliff White
2003-02-17 23:13 ` 2.5.61-mm1 Matthew Wilcox
2003-02-17 23:52   ` 2.5.61-mm1 Cliff White

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=3E4DEB72.4010405@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.