RE: Dual CPU for Linux 7.2

As per Stew's top output below, I stand corrected on TOP's CPU capabilities.
It does show at least a one liner per cpu.
The unfortunately consequence of stupidly running TOP here on a single
processor system....
rather than one of my SMP systems. Can you say "duh!" ?

It can be used to monitor cpu levels on a per cpu basis.

if you are not seeing multiple CPU's in TOP, then you are not running the
SMP kernel
and need to change the boot time selection to the proper version.


++> -----Original Message-----
++> From: [email protected]
++> [mailto:[email protected]]On Behalf Of Stewart M. Ives
++> Sent: Thursday, March 06, 2003 11:28 AM
++> To: [email protected]
++> Subject: RE: Dual CPU for Linux 7.2
++>
++>
++> [email protected] wrote:
++> >> Hello folks,
++> >>
++> >> I've just installed RH 7.2 on Intel workstation
++> >> with two Xeon processors.
++> >>
++> >> I have no indication that RH utilizes both processors.
++> It seems that
++> >> only one runs. gmesg shows only cpu#0 initialization,
++> >> gtop shows only one cpu.
++> >>
++> >> Maybe sombedy faced similar problem? How should i
++> >> configure system to run on two cpus?
++> >>
++> >> Thanks for your contribution,
++> >> Gary.
++> >
++> > You're assumming that both CPUs should be running all the
++> time. This
++> > is not the case. The second CPU shouldn't kick in until
++> the first is
++> > taxed. What you have to do is overload the first CPU
++> while monitoring
++> > with something like top.
++> >
++> > Open a few shells with database queries that run and then some
++> > graphics apps, something really CPU intensive. That may
++> kick in the
++> > second puter. If not, and if you can sit at the console
++> and kill the
++> > machine, there is a null command replicator string that
++> you can run
++> > in a shell that will respawn itself over and over. This
++> used to work
++> > on older machines, whether it will work on newer systems
++> with a ton
++> > of power is to be seen. Maybe you can tell us? :)
++> >
++> > Here's the string. *_Do _Not_* run this on a production
++> system. You've
++> > been warned.
++> >          :(){ :|:& };:
++> >
++> > What this lines tries to do is to keep on loading null
++> command, after
++> > null command, and it also pipes them to each other.
++> Notice the '|',
++> > which does the piping in between the null shells.
++> >
++> > This runs in the background, in order to slow down the system even
++> > more. Basically, this program just tries to load empty
++> shell, after
++> > another one, until your operating system realizes that
++> you have too
++> > many of them open, and it tries to close them.
++> >
++> > Let us know what the results are. I'm curious.
++> >
++> > Cheers!
++>
++> Fans,
++>
++> top should at least show both cpu's.  Here is sample output:
++>
++>  11:25am  up 6 days,  9:08,  3 users,  load average: 0.00,
++> 0.02, 0.00
++> 74 processes: 70 sleeping, 4 running, 0 zombie, 0 stopped
++> CPU0 states:  1.2% user,  1.0% system,  0.0% nice, 97.1% idle
++> CPU1 states:  2.0% user,  0.2% system,  0.0% nice, 97.2% idle
++> Mem:   513476K av,  488816K used,   24660K free,       0K
++> shrd,   72244K
++> buff
++> Swap:  842680K av,       0K used,  842680K free
++>      344924K
++> cached
++>
++> If this guy is not even getting the 2nd CPU showing up in
++> top then the
++> problem is elsewhere.
++>
++> If you don't have the 2nd CPU showing up in top is it
++> enabled in your
++> BIOS??
++>
++> When you boot the machine do both CPU's get listed on the
++> initial BIOS
++> screen at bootup??
++>
++> stew
++>
++>
++> ---
++> Outgoing SofTEC USA mail is certified Virus Free.
++> Checked by AVG anti-virus system (http://www.grisoft.com).
++> Version: 6.0.459 / Virus Database: 258 - Release Date: 2/25/2003
++>
++>
++>
++>
++> _______________________________________________
++> enigma-list mailing list
++> [email protected]
++> https://listman.redhat.com/mailman/listinfo/enigma-list
++>