From: Catalin BOIE <util@deuroconsult.ro>
To: Nick Piggin <piggin@cyberone.com.au>
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 13:48:28 +0200 (EET) [thread overview]
Message-ID: <Pine.LNX.4.58.0311131345140.4183@hosting.rdsbv.ro> (raw)
In-Reply-To: <3FB36E18.2030105@cyberone.com.au>
> Hi,
Hi!
> Please capture a Ctrl + Scroll Lock dump when you get processes stuck in
> D state.
I will.
> >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
Do you think that disabling HT (how I do it? noht?) will make things works
better? I suspect that a process is scheduled on a virtual processor that
doesn't get much chances to execute something. I don't know.
> 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).
The problem with HT is the one that I describe here. From time to time a
process (mc, bash) is stuck for 2-6 seconds and then comes back. In test8
this was more visible.
Thank you very much, Nick!
---
Catalin(ux) BOIE
catab@deuroconsult.ro
next prev parent reply other threads:[~2003-11-13 11:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 11:12 Catalin BOIE
2003-11-13 11:42 ` Nick Piggin
2003-11-13 11:48 ` Catalin BOIE [this message]
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=Pine.LNX.4.58.0311131345140.4183@hosting.rdsbv.ro \
--to=util@deuroconsult.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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
all inboxes | Powered by JetHome®