From: "Timothy Miller" <tmiller10@cfl.rr.com>
To: <linux-kernel@vger.kernel.org>
Subject: Quick question about hyper-threading
Date: Sat, 12 Apr 2003 23:13:57 -0400 [thread overview]
Message-ID: <000701c3016a$b9d76c90$6801a8c0@epimetheus> (raw)
On a hyper-threaded CPU, it seems to me that there could be a lot of
cache-thrashing if the two processes running are completely unrelated. On
the other hand, if one process has two threads, then they would benefit (or
hurt less) from the cache-sharing, because they share the same memory space.
Does the HT-aware scheduler attempt to take this into account by scheduling
two related threads to run simultaneously on the same CPU as often as
possible (unless you're in a multi-processor system and another CPU would
otherwise be idle)?
next reply other threads:[~2003-04-13 2:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-13 3:13 Timothy Miller [this message]
2003-04-13 4:06 ` Quick question about hyper-threading Robert Love
[not found] <20030413031007$5a6f@gated-at.bofh.it>
[not found] ` <20030413041007$6d72@gated-at.bofh.it>
2003-04-13 9:06 ` Tony 'Nicoya' Mantler
2003-04-14 14:46 ` Martin J. Bligh
-- strict thread matches above, loose matches on Subject: below --
2003-04-13 22:13 Chuck Ebbert
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='000701c3016a$b9d76c90$6801a8c0@epimetheus' \
--to=tmiller10@cfl.rr.com \
--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