All of lore.kernel.org
 help / color / mirror / Atom feed
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 23:03:54 +1100	[thread overview]
Message-ID: <3FB3732A.4060604@cyberone.com.au> (raw)
In-Reply-To: <Pine.LNX.4.58.0311131345140.4183@hosting.rdsbv.ro>



Catalin BOIE wrote:

>>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.
>

I can't see an option to just disable HT with a quick grep. acpi=off
should do it though.

The virtual processors should get a roughly even amount of work done
AFAIK. I don't think the P4 allows any sort of control over priorities.

>
>>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!
>

Oh, so it is not any sort of disk IO work that is getting stuck? Then
don't worry about getting the Ctrl Scroll Lock trace...

OK, well yes turn HT off and see if that helps. One other thing which
springs to mind is that there is some CPU scheduler code that increases
timeslice grainularity as the CPU count increases. It seems a bit unlikely
that this is your problem though.



  reply	other threads:[~2003-11-13 12:04 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
2003-11-13 11:48   ` Catalin BOIE
2003-11-13 12:03     ` Nick Piggin [this message]
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=3FB3732A.4060604@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.