From: Chuck Ebbert <76306.1226@compuserve.com>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Quick question about hyper-threading
Date: Sun, 13 Apr 2003 18:13:24 -0400 [thread overview]
Message-ID: <200304131817_MC3-1-3444-7E30@compuserve.com> (raw)
Rovert Love wrote:
> No, the current scheduler (HT or stock 2.5) does not do
> this.
>
> Your theories are correct. It would be interesting to try
> this and see.
>
> It is nontrivial to do the ->mm checks in the scheduler though -
> certainly they cannot be done easily (if at all) in constant-time
> (i.e., it won't be O(1)).
Is the scheduler even the right place to do that?
I was thinking maybe the task_struct could use a cpus_desired
field -- then other parts of the system could give the scheduler hints
about which CPU to schedule a task on.
--
Chuck
next reply other threads:[~2003-04-13 22:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-13 22:13 Chuck Ebbert [this message]
[not found] <20030413031007$5a6f@gated-at.bofh.it>
[not found] ` <20030413041007$6d72@gated-at.bofh.it>
2003-04-13 9:06 ` Quick question about hyper-threading Tony 'Nicoya' Mantler
2003-04-14 14:46 ` Martin J. Bligh
-- strict thread matches above, loose matches on Subject: below --
2003-04-13 3:13 Timothy Miller
2003-04-13 4:06 ` Robert Love
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=200304131817_MC3-1-3444-7E30@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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