public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Help understanding slow down
Date: Tue, 25 May 2004 12:32:38 +0200	[thread overview]
Message-ID: <20040525103238.GA4212@elte.hu> (raw)
In-Reply-To: <20040524005331.71465614.akpm@osdl.org>


* Andrew Morton <akpm@osdl.org> wrote:

> But if you _are_ using poll_idle() and if your CPU is hyperthreaded
> then yes, one "CPU" is going to take a performance hit from the "idle"
> one.

with the patch below we will print a big fat warning. (I did not want to
deny idle=poll altogether - future HT implementations might work fine
with polling idle.)

	Ingo

Signed-off-by: Ingo Molnar <mingo@elte.hu>

--- linux/arch/i386/kernel/process.c.orig	
+++ linux/arch/i386/kernel/process.c	
@@ -202,6 +202,10 @@ static int __init idle_setup (char *str)
 	if (!strncmp(str, "poll", 4)) {
 		printk("using polling idle threads.\n");
 		pm_idle = poll_idle;
+#ifdef CONFIG_SMP
+		if (smp_num_siblings > 1)
+			printk("WARNING: polling idle and HT enabled, performance may degrade.\n");
+#endif
 	} else if (!strncmp(str, "halt", 4)) {
 		printk("using halt in idle threads.\n");
 		pm_idle = default_idle;

  parent reply	other threads:[~2004-05-25  9:21 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-24  0:32 Help understanding slow down Phy Prabab
2004-05-24  0:57 ` Phy Prabab
2004-05-24  1:04   ` William Lee Irwin III
2004-05-24  1:25     ` Jakob Oestergaard
2004-05-24  1:28       ` William Lee Irwin III
2004-05-24  1:51         ` Phy Prabab
2004-05-24  2:42           ` Nick Piggin
2004-05-24  2:43           ` Andrew Morton
2004-05-24  6:23             ` Phy Prabab
2004-05-24  6:27               ` William Lee Irwin III
2004-05-24  6:39                 ` Phy Prabab
2004-05-24  7:21                   ` Phy Prabab
2004-05-24  7:44                     ` Nick Piggin
2004-05-24  7:50                       ` Phy Prabab
2004-05-24  7:59                         ` Nick Piggin
2004-05-24 10:43                           ` Jakob Oestergaard
2004-05-24 14:13                     ` Martin J. Bligh
2004-05-24  7:53                   ` Andrew Morton
2004-05-24  8:00                     ` Phy Prabab
2004-05-25 10:32                     ` Ingo Molnar [this message]
2004-05-25  9:29                       ` Andrew Morton
2004-05-25 11:42                         ` Ingo Molnar
2004-05-25  9:58                           ` Andrew Morton
2004-05-25 12:25                             ` Ingo Molnar
2004-05-24  6:33   ` Paul Rolland
2004-05-24 17:28     ` Roger Luethi
  -- strict thread matches above, loose matches on Subject: below --
2004-05-24  1:37 Robert M. Stockmann
2004-05-24  1:50 ` Phy Prabab
2004-05-24  3:31 ` Robert M. Stockmann
2004-05-24  6:14   ` Phy Prabab
2004-05-24 18:36     ` Robert M. Stockmann

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=20040525103238.GA4212@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@osdl.org \
    --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