From: "Renato" <webmaster@cienciapura.com.br>
To: "Reed, Timothy A" <timothy.a.reed@lmco.com>,
"Linux Kernel ML \(E-mail\)" <linux-kernel@vger.kernel.org>
Subject: Re: Hyperthreading Options in 2.4.19
Date: Wed, 7 Aug 2002 17:39:36 [thread overview]
Message-ID: <20020807203936.14257.qmail@hm36.locaweb.com.br> (raw)
In-Reply-To: <9EFD49E2FB59D411AABA0008C7E675C009D8DEE3@emss04m10.ems.lmco.com>
I read a while back that the kernel boot parameter "idle=poll" helps to improve the wake up latency of processes in high
performance systems.
On Wed, 07 Aug 2002 14:22:05 -0400, "Reed, Timothy A" <timothy.a.reed@lmco.com> escreveu :
> De: "Reed, Timothy A" <timothy.a.reed@lmco.com>
> Data: Wed, 07 Aug 2002 14:22:05 -0400
> Para: "Linux Kernel ML (E-mail)" <linux-kernel@vger.kernel.org>
> Assunto: Hyperthreading Options in 2.4.19
>
> Hello All,
> I am going rounds with a sub-contractor of ours about what options
> should and should not be compiled into the kernel in order for
> Hyperthreading to work. Can anyone make any suggestions and comments to the
> options (below) that I am planning on enforcing:
> MSR
> MTRR
> CPUID
>
> Lilo.conf : acpismp=force??
>
> Are the following worth any thing of value to Hyperthreading:
> Microcode
> ACPI
>
> TIA
>
> Timothy Reed
> Software Engineer/Systems Administrator
> Lockheed Martin - NE & SS Syracuse
> Email: timothy.a.reed@lmco.com
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
>
next prev parent reply other threads:[~2002-08-07 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 18:22 Reed, Timothy A
2002-08-07 17:39 ` Renato [this message]
2002-08-07 22:36 ` J.A. Magallon
2002-08-08 10:55 Reed, Timothy A
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=20020807203936.14257.qmail@hm36.locaweb.com.br \
--to=webmaster@cienciapura.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=timothy.a.reed@lmco.com \
/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®