All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brandon Low <lostlogic@gentoo.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: anticipatory scheduler merged
Date: Sun, 6 Jul 2003 21:22:13 -0500	[thread overview]
Message-ID: <20030707022212.GE27027@lostlogicx.com> (raw)
In-Reply-To: <20030705133334.4cc7e11b.akpm@osdl.org>

On Sat, 07/05/03 at 13:33:34 -0700, Andrew Morton wrote:
> - These changes have been well tested, but it is five months work and
>   over 100 patches.  There's probably a bug or two.  If you suspect that
>   something has gone wrong at the block layer (lots of tasks stuck in D
>   state) then please retest with `elevator=deadline'.
> 
> Thanks.

I am seeing these D tasks when running 2.5.74-mm2 under a heavy seeking
load (compiling application, untarring kernel, and filesharing
simultaneously) on a slow (laptop 4200RPM) hdd.  I find that after about
10 uptime when I start throwing on the seeking loads one or all of them
go to D state and any new disk IO is either blocked or very slow.

I have tested with elevator=deadline and have been unable to reproduce.

Any further testing or debugging you need me to do I can probably do
(but I'm not terribly knowledgable so I'll need step by step for said
testing).  Thanks!

Brandon Low

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-05 20:33 anticipatory scheduler merged Andrew Morton
2003-07-07  2:22 ` Brandon Low [this message]
2003-07-07  2:37   ` Nick Piggin
2003-07-07  8:24 ` James H. Cloos Jr.
2003-07-07  8:33   ` Nick Piggin
2003-07-07  8:36   ` Andrew Morton

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=20030707022212.GE27027@lostlogicx.com \
    --to=lostlogic@gentoo.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.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.