From: Mike Sullivan <mike.sullivan@alltec.com>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Scheduling with Hyperthreading
Date: Tue, 25 Feb 2003 16:23:25 -0500 [thread overview]
Message-ID: <3E5BDECD.40502@alltec.com> (raw)
In-Reply-To: Pine.LNX.4.44.0302251616300.31810-100000@coffee.psychology.mcmaster.ca
I have tried RH 2.4.18 stock redhat kernels and and 2.4.20 kernels. Both
seem to
do badly.
Is there somewhere to look to see a history of the schedular work, or do
I need
to puruse all of the changelogs to get an idea of what kernel I should
be trying.
Regards
Mike
Mark Hahn wrote:
>>I would to a quick snap with top, and when I saw 99.9% I assumed the the
>>process had
>>been there during the time top was starting up.
>>
>>Looking at /proc/(pid)/cpu, shows that with two jobs running they are
>>sticking to cpu 0 and 1
>>which are siblings
>>
>>
>
>ah, sorry if you said this, but which kernel are you running?
>you need a HT-aware scheduler, for sure. does your problem go away
>if you boot with noht?
>
>
--
----------------------------------------------------------------------
Mike Sullivan Director Performance Computing
@lliance Technologies, Voice: (416) 385-3255,
18 Wynford Dr, Suite 407 Fax: (416) 385-1774
Toronto, ON, Canada, M3C-3S2 Toll Free:1-877-216-3199
http://www.alltec.com
next parent reply other threads:[~2003-02-25 21:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0302251616300.31810-100000@coffee.psychology.mcmaster.ca>
2003-02-25 21:23 ` Mike Sullivan [this message]
2003-02-25 21:21 Scheduling with Hyperthreading Pallipadi, Venkatesh
[not found] <Pine.LNX.4.44.0302250852190.26386-100000@coffee.psychology.mcmaster.ca>
2003-02-25 21:01 ` Mike Sullivan
-- strict thread matches above, loose matches on Subject: below --
2003-02-25 7:43 Mike Sullivan
2003-02-25 1:04 Scheduling with HyperThreading Mike Sullivan
2003-02-25 5:45 ` James Bourne
2003-02-25 5:59 ` William Lee Irwin III
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=3E5BDECD.40502@alltec.com \
--to=mike.sullivan@alltec.com \
--cc=hahn@physics.mcmaster.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox