From: "Kevin J. Cummings" <cummings@kjchome.homeip.net>
To: "Matías López Bergero" <mlopezb@udesa.edu.ar>
Cc: linux-admin <linux-admin@vger.kernel.org>
Subject: Re: smp question
Date: Tue, 30 Nov 2004 11:56:21 -0500 [thread overview]
Message-ID: <41ACA635.4040204@kjchome.homeip.net> (raw)
In-Reply-To: <41AC74C8.8090405@udesa.edu.ar>
Matías López Bergero wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Kevin J. Cummings wrote:
> | Matías López Bergero wrote:
> |> I have a SMP capable server, but with only one cpu installed.
> |> Should I enable SMP support on the kernel? I'm trying to reach the best
> |> performance.
> |> The cpu is Intel Xeon, this option is not in the cpu list in the kernel
> |> config. Should I chose P4 or P3? it is the same?
> |
> | IIRC, Xeon processors have dual internal cores (or at least dual
> | instruction decode paths), and act like dual processors, and benefit
> | from the SMP kernels. Also, IIRC, there were both P3 and P4 Xeons made.
> | So, you have to know which version you have.
> |
> | What does "cat /proc/cpuinfo" tell you?
> |
>
> I'm seeing two processors, I had notes this before, but I was in doubt
> if that output was produced by the SMP kernel, or the Xeon cpu, now
> according to what you are telling me, it's a feature of the Xeon cpu right?
If I remember Correctly, yes, its a feature of the XEON CPU. (I have
athlons here at home!)
> Here is my cpuinfo:
>
> sh-2.05b# cat /proc/cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 15
> model : 2
> model name : Intel(R) Xeon(TM) CPU 2.80GHz
This looks like a P4 Xeon: 2.80GHz speed
> stepping : 9
> cpu MHz : 2800.195
> cache size : 512 KB
> physical id : 0
> siblings : 2
Yeup, looks like 2 instruction pipelines.
> runqueue : 0
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 2
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2
> ss ht tm
> bogomips : 5583.66
And the second "processor":
> processor : 1
> vendor_id : GenuineIntel
> cpu family : 15
> model : 2
> model name : Intel(R) Xeon(TM) CPU 2.80GHz
> stepping : 9
> cpu MHz : 2800.195
> cache size : 512 KB
> physical id : 0
> siblings : 2
> runqueue : 0
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 2
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2
> ss ht tm
> bogomips : 5596.77
>
> sh-2.05b#
>
> Thanks for ur help Kevin!
NP
--
Kevin J. Cummings
kjchome@rcn.com
cummings@kjchome.homeip.net
cummings@kjc386.framingham.ma.us
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2004-11-30 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 17:04 smp question Matías López Bergero
2004-11-29 23:56 ` Kevin J. Cummings
2004-11-30 13:25 ` Matías López Bergero
2004-11-30 16:56 ` Kevin J. Cummings [this message]
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=41ACA635.4040204@kjchome.homeip.net \
--to=cummings@kjchome.homeip.net \
--cc=linux-admin@vger.kernel.org \
--cc=mlopezb@udesa.edu.ar \
/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;
as well as URLs for NNTP newsgroup(s).