From: "J.A. Magallon" <jamagallon@able.es>
To: "Reed, Timothy A" <timothy.a.reed@lmco.com>
Cc: "Linux Kernel ML (E-mail)" <linux-kernel@vger.kernel.org>
Subject: Re: Hyperthreading Options in 2.4.19
Date: Thu, 8 Aug 2002 00:36:36 +0200 [thread overview]
Message-ID: <20020807223636.GC1537@werewolf.able.es> (raw)
In-Reply-To: <9EFD49E2FB59D411AABA0008C7E675C009D8DEE3@emss04m10.ems.lmco.com>; from timothy.a.reed@lmco.com on Wed, Aug 07, 2002 at 20:22:05 +0200
On 2002.08.07 "Reed, Timothy A" wrote:
>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
I thikn none is needed for ht. Of course, mtrr raises performance.
The other are not needed, afaik.
>
> Lilo.conf : acpismp=force??
>
True for old kernels, not needed anymore.
> Are the following worth any thing of value to Hyperthreading:
> Microcode
> ACPI
No.
In summary, with 2.4.19 you do not have to do nothing to have hyperthreading.
Other useful options are 'noht' to disable ht, and 'idle=poll', that I think
improves latency.
by
--
J.A. Magallon <jamagallon@able.es> \ Software is like sex:
werewolf.able.es \ It's better when it's free
Mandrake Linux release 9.0 (Cooker) for i586
Linux 2.4.20-pre1-jam1 (gcc 3.2 (Mandrake Linux 9.0 3.2-0.2mdk))
next prev parent reply other threads:[~2002-08-07 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 18:22 Hyperthreading Options in 2.4.19 Reed, Timothy A
2002-08-07 17:39 ` Renato
2002-08-07 22:36 ` J.A. Magallon [this message]
-- strict thread matches above, loose matches on Subject: below --
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=20020807223636.GC1537@werewolf.able.es \
--to=jamagallon@able.es \
--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