From: Brad Fitzpatrick <brad@danga.com>
To: Michael Tewner <tewner@jct.ac.il>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux SMT question
Date: Wed, 29 Dec 2004 03:22:53 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0412290319180.17218@danga.com> (raw)
In-Reply-To: <41D289A6.7050805@jct.ac.il>
Michael,
On Wed, 29 Dec 2004, Michael Tewner wrote:
> I'm sorry if this has been covered before. If it has, please direct me
> on where to look.
>
> Over the year, our university started acquiring dual Xeon servers. I
> havn't been able to find consistent information regarding how linux
> deals with the SMT (HT?).
Check out this article:
http://lwn.net/Articles/80911/
lwn.net's a great source of both news and timely explanations of kernel
changes underway.
> Finally, is there a way to force an application to run an separate
> physical CPU's? Perhaps a MOSIX-like /proc interface (where each PID has
> a special file with preferences such as keep-local)?
$ man 2 sched_setaffinity
- Brad
prev parent reply other threads:[~2004-12-29 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-29 10:40 Michael Tewner
2004-12-29 11:22 ` Brad Fitzpatrick [this message]
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.0412290319180.17218@danga.com \
--to=brad@danga.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tewner@jct.ac.il \
/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®