From: Nick Piggin <piggin@cyberone.com.au>
To: Catalin BOIE <util@deuroconsult.ro>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0test9 + 2 * P IV Xeon 2.4GHz with HT + SATA + RAID1 = scheduler problems
Date: Thu, 13 Nov 2003 22:42:16 +1100 [thread overview]
Message-ID: <3FB36E18.2030105@cyberone.com.au> (raw)
In-Reply-To: <Pine.LNX.4.58.0311131303500.4183@hosting.rdsbv.ro>
Catalin BOIE wrote:
>Hi!
>
>I want to tell you that 2.6.0-test gets better and better. It works very
>very well on several systems. Thank you very much, guys.
>
>I have an server (like in the subject). The problem is that the scheduler
>seems to behave weird. Sometimes a program just do nothing. There is no
>disk activity, interrupts are a little over 1000, no disk requests,
>context switches are ~40. The system is idle but it has work to do!
>Can I provide more info?
>
>I tried to put elevator=deadline and things seems worse.
>
>If I'm not mistaken, the processes are in D state. Bt I'm not sure, I must
>check again and right now I can't.
>
Hi,
Please capture a Ctrl + Scroll Lock dump when you get processes stuck in
D state.
>
>Also I suspect that scheduler doesn't pay special attention to virtual
>(HT) processors. Is this true?
>
This is correct. Are you seeing any problems with HT? I think Linus
was hoping the NUMA / SMP scheduler could be generalised a bit more
so that HT would just fall into place. This might not happen before
2.7, so the shared runqueue approach might be the next best thing
(I like it).
next prev parent reply other threads:[~2003-11-13 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 11:12 2.6.0test9 + 2 * P IV Xeon 2.4GHz with HT + SATA + RAID1 = scheduler problems Catalin BOIE
2003-11-13 11:42 ` Nick Piggin [this message]
2003-11-13 11:48 ` Catalin BOIE
2003-11-13 12:03 ` Nick Piggin
2003-11-13 12:12 ` Catalin BOIE
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=3FB36E18.2030105@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=util@deuroconsult.ro \
/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.