From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: Context switch times
Date: Mon, 8 Oct 2001 11:19:49 -0400 [thread overview]
Message-ID: <200110081519.f98FJnZ10592@deathstar.prodigy.com> (raw)
In-Reply-To: <3BC067BB.73AF1EB5@welho.com>
In article <3BC067BB.73AF1EB5@welho.com> Mika.Liljeberg@welho.com wrote:
>Yes. However, you still want to balance the queues even if all CPUs are
>100% utilized. It's a fairness issue. Otherwise you could have 1 task
>running on one CPU and 49 tasks on another.
You say that as if it were a bad thing... I believe that if you have
one long running task and many small tasks in the system CPU affinity
will make that happen now. Obviously not if all CPUs are 100% loaded,
and your 1 vs. 49 is unrealistic, but having a task stay with a CPU
while trivia run on other CPU(s) is generally a good thing under certain
load conditions, which I guess are no less likely than your example;-)
--
bill davidsen <davidsen@tmr.com>
"If I were a diplomat, in the best case I'd go hungry. In the worst
case, people would die."
-- Robert Lipe
next prev parent reply other threads:[~2001-10-08 15:19 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-04 21:04 Mike Kravetz
2001-10-04 21:14 ` arjan
2001-10-04 21:39 ` Richard Gooch
2001-10-09 4:55 ` Richard Gooch
2001-10-09 13:49 ` bill davidsen
2001-10-04 21:25 ` David S. Miller
2001-10-04 21:52 ` David S. Miller
2001-10-04 21:55 ` Benjamin LaHaise
2001-10-04 22:35 ` Davide Libenzi
2001-10-04 22:49 ` Mike Kravetz
2001-10-04 22:42 ` Linus Torvalds
2001-10-04 22:53 ` Benjamin LaHaise
2001-10-05 15:13 ` Alan Cox
2001-10-05 17:49 ` george anzinger
2001-10-05 22:29 ` Alan Cox
2001-10-05 22:56 ` Davide Libenzi
2001-10-05 23:04 ` Alan Cox
2001-10-05 23:16 ` Davide Libenzi
2001-10-05 23:17 ` Alan Cox
2001-10-05 23:21 ` Davide Libenzi
2001-10-05 23:43 ` Roger Larsson
2001-10-07 1:20 ` george anzinger
2001-10-07 1:33 ` Bill Davidsen
2001-10-07 9:56 ` Alan Cox
2001-10-06 2:24 ` Albert D. Cahalan
2001-10-06 2:57 ` Davide Libenzi
2001-10-07 9:57 ` Mika Liljeberg
2001-10-07 13:03 ` Ingo Oeser
2001-10-07 13:48 ` Mika Liljeberg
2001-10-07 14:24 ` Ingo Oeser
2001-10-07 14:33 ` Mika Liljeberg
2001-10-07 18:00 ` george anzinger
2001-10-07 22:06 ` Mika Liljeberg
2001-10-07 22:31 ` Davide Libenzi
2001-10-07 22:33 ` Mika Liljeberg
2001-10-07 23:49 ` george anzinger
2001-10-08 21:07 ` Mika Liljeberg
2001-10-08 22:54 ` discontig physical memory Petko Manolov
2001-10-08 23:05 ` David S. Miller
2001-10-08 23:18 ` Petko Manolov
2001-10-08 23:29 ` David S. Miller
2001-10-09 0:34 ` Petko Manolov
2001-10-09 0:36 ` Petko Manolov
2001-10-09 1:37 ` David S. Miller
2001-10-09 2:43 ` Petko Manolov
2001-10-08 15:19 ` bill davidsen [this message]
2001-10-10 6:07 ` Context switch times Mike Fedyk
2001-10-07 18:39 ` Davide Libenzi
2001-10-09 20:37 ` Hubertus Franke
2001-10-09 23:50 ` george anzinger
2001-10-11 10:52 ` Hubertus Franke
2001-10-04 23:41 ` Mike Kravetz
2001-10-04 23:50 ` Linus Torvalds
2001-10-05 15:15 ` Eric W. Biederman
2001-10-04 23:56 ` Davide Libenzi
2001-10-05 0:45 ` Andrea Arcangeli
2001-10-05 4:35 ` Mike Kravetz
2001-10-07 17:59 ` Andrea Arcangeli
2001-10-07 19:54 ` george anzinger
2001-10-07 20:24 ` Andrea Arcangeli
2001-10-09 5:00 ` David S. Miller
2001-10-05 6:31 Michailidis, Dimitrios
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=200110081519.f98FJnZ10592@deathstar.prodigy.com \
--to=davidsen@tmr.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
all inboxes | Powered by JetHome®