From: Mike Sullivan <mike.sullivan@alltec.com>
To: Mark Hahn <hahn@physics.mcmaster.ca>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Scheduling with Hyperthreading
Date: Tue, 25 Feb 2003 16:01:22 -0500 [thread overview]
Message-ID: <3E5BD9A2.6090705@alltec.com> (raw)
In-Reply-To: Pine.LNX.4.44.0302250852190.26386-100000@coffee.psychology.mcmaster.ca
Mark
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
Regards
Mike
Mark Hahn wrote:
>>that if I run two compute intensive jobs on a Dual Xeon, the processes
>>run on separate
>>physical cpus and can spend a significant amount of time with both on a
>>single
>>cpu.
>>
>>
>
>how did you determine this? running another program, such as top,
>will naturally disturb the scheduler and corrupt any observations.
>the only means I can think of is to look in /proc/<pid>/cpu near
>very infrequently (ideally, just before the processes exit.)
>or is this what you've done?
>
>
--
----------------------------------------------------------------------
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 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0302250852190.26386-100000@coffee.psychology.mcmaster.ca>
2003-02-25 21:01 ` Mike Sullivan [this message]
[not found] <Pine.LNX.4.44.0302251616300.31810-100000@coffee.psychology.mcmaster.ca>
2003-02-25 21:23 ` Scheduling with Hyperthreading Mike Sullivan
2003-02-25 21:21 Pallipadi, Venkatesh
-- 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=3E5BD9A2.6090705@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 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.