Number of CPU & Number of Core


 
Thread Tools Search this Thread
Operating Systems AIX Number of CPU & Number of Core
Prev   Next
# 1  
Old 02-13-2013
Number of CPU & Number of Core

HTML Code:
root:/> 
# lscfg -vp|grep -c -E 'proc.*Processor'
8
root:/> 
# lscfg -vpl sysplanar0 | grep -i way
      8 WAY PROC CUOD :
      8 WAY PROC CUOD :
      8 WAY PROC CUOD :
      8 WAY PROC CUOD :
      8 WAY PROC CUOD :
      8 WAY PROC CUOD :
I have this output and need to know how to interpret.
The number of CPU is 8 for sure. When you say the number of Cores, what is it in this case? lscfg -vpl sysplanar0 | grep -i way shows 8 WAY PROC CUOD, so is it 8 Cores?

An old machine (model: IBM,9111-520) shows 2 CPUs, but no result on lscfg -vpl sysplanar0 | grep -i way. In that case, it has no Core??

Please advise.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Number of CPU'S in UNIX box

Hi, How to find number of CPU'S in unix box. And usage of the total no of CPU'S. (7 Replies)
Discussion started by: sam1226
7 Replies

2. HP-UX

How to find number of CPU in system

$ uname -a HP-UX chd007d B.11.23 U 9000/800 3154283600 unlimited-user license Thanks (7 Replies)
Discussion started by: Maddy123
7 Replies

3. Solaris

How to check number of "CPU physical and core"?

Hi All, How to check number of "CPU physical and core" ? my machine is T5240, T5440 I try to user prtdiag it show 128 CPUs ?? what real number for it? (5 Replies)
Discussion started by: arm_naja
5 Replies

4. Red Hat

Number of CPU in LINUX server

I want to find number of CPU and number NIC card in Linux server. I have below content in /proc/cpuinfo. I have from processor 0 - 15. It means, i have 15 similar entries in that file. How many CPU we have on this server? also how do find how many NIC card on this? processor : 0... (5 Replies)
Discussion started by: govindts
5 Replies

5. Red Hat

Number of CPU in linux server

I am using linux server.. how do i see number of CPU's in the server? TOP command is not providing result.. Any help is highly appreciated. (8 Replies)
Discussion started by: govindts
8 Replies

6. Solaris

Number of CPU

Hi Experts, with the help of which command we can see the Number of cpu in a solaris solaris5.10.Also how we know the total disk & free disk space size in this system. Kind regards ---------- Post updated at 12:25 PM ---------- Previous update was at 12:25 PM ---------- Command... (10 Replies)
Discussion started by: rafiassam
10 Replies

7. UNIX for Dummies Questions & Answers

Display just CPU run queue number (Nothing Else)

Im using the vmstat command to display the CPU run queue, but i want to put that into a program so is there a way to just display the number under the r? Thanks, (1 Reply)
Discussion started by: RAFC_99
1 Replies

8. Solaris

[help] how to get serial number of cpu or other hardware

hi experts, hi all, need help, how to get serial number of cpu or other hardware using command? does anybody know using what syntax? thank you wu (8 Replies)
Discussion started by: bucci
8 Replies

9. Solaris

CPU Usage to Number of CPUs - relationship

I have an E15K running at 60% CPU usage on 16 CPUs. I need to get rid of 6 CPUs, which is 38%. Does that mean my CPU usage will go up to 98%? I suspect the relationship between CPU numbers and usage is a bit more complicated. Can anyone give me any guidance on this please? TIA (0 Replies)
Discussion started by: disturbed_uk
0 Replies

10. Solaris

number of cpu's

How can I tell how many cpu's are on a solaris 9 sunfire? (3 Replies)
Discussion started by: csaunders
3 Replies
Login or Register to Ask a Question
CYCLICTEST(8)						      System Manager's Manual						     CYCLICTEST(8)

NAME
cyclictest - High resolution test program SYNOPSIS
cyclictest [ -hfmnqrsvMS ] [-a proc ] [-b usec ] [-c clock ] [-d dist ] [-h histogram ] [-i intv ] [-l loop ] [-o red ] [-p prio ] [-t num ] [-D time] [-w] [-W] [-y policy ] [ -S | -U ] OPTIONS
These programs follow the usual GNU command line syntax, with long options starting with two dashes ('--'). A summary of options is included below. -a, --affinity[=PROC] Run all threads on procesor number PROC. If PROC is not specified, run thread #N on processor #N. -b, --breaktrace=USEC Send break trace command when latency > USEC. This is a debugging option to control the latency tracer in the realtime preemption patch. It is useful to track down unexpected large latencies on a system. This option does only work with following kernel config options. For kernel < 2.6.24: * CONFIG_PREEMPT_RT=y * CONFIG_WAKEUP_TIMING=y * CONFIG_LATENCY_TRACE=y * CONFIG_CRITICAL_PREEMPT_TIMING=y * CONFIG_CRITICAL_IRQSOFF_TIMING=y For kernel >= 2.6.24: * CONFIG_PREEMPT_RT=y * CONFIG_FTRACE * CONFIG_IRQSOFF_TRACER=y * CONFIG_PREEMPT_TRACER=y * CONFIG_SCHED_TRACER=y * CONFIG_WAKEUP_LATENCY_HIST kernel configuration options enabled. The USEC parameter to the -b option defines a maximum latency value, which is compared against the actual latencies of the test. Once the measured latency is higher than the given maximum, the kernel tracer and cyclictest is stopped. The trace can be read from /proc/latency_trace. Please be aware that the tracer adds significant overhead to the kernel, so the latencies will be much higher than on a kernel with latency tracing disabled. -c, --clock=CLOCK Selects the clock, which is used: * 0 selects CLOCK_MONOTONIC, which is the monotonic increasing system time (default). * 1 selects CLOCK_REALTIME, which is the time of day time. CLOCK_REALTIME can be set by settimeofday, while CLOCK_MONOTONIC can not be modified by the user. This option has no influence when the -s option is given. -C, --context context switch tracing (used with -b) -d, --distance=DIST Set the distance of thread intervals in microseconds (default is 500us). When cyclictest is called with the -t option and more than one thread is created, then this distance value is added to the interval of the threads: Interval(thread N) = Interval(thread N-1) + DIST -E, --event event tracing (used with -b) -f, --ftrace Enable function tracing using ftrace as tracer. This option is available only with -b. -h, --histogram=MAXLATENCYINUS Dump latency histogram to stdout. US means the max time to be be tracked in microseconds. When you use -h option to get histogram data, Cyclictest runs many threads with same priority without priority--. -H, --histofall=MAXLATENCYINUS Same as -h except that an additional histogram column is displayed at the right that contains summary data of all thread histograms. If cyclictest runs a single thread only, the -H option is equivalent to -h. -i, --interval=INTV Set the base interval of the thread(s) in microseconds (default is 1000us). This sets the interval of the first thread. See also -d. -l, --loops=LOOPS Set the number of loops. The default is 0 (endless). This option is useful for automated tests with a given number of test cycles. Cyclictest is stopped once the number of timer intervals has been reached. -n, --nanosleep Use clock_nanosleep instead of posix interval timers. Setting this option runs the tests with clock_nanosleep instead of posix interval timers. -N, --nsecs Show results in nanoseconds instead of microseconds, which is the default unit. -o, --oscope=RED Oscilloscope mode, reduce verbose output by RED. -O, --traceopt=TRACING_OPTION Used to pass tracing options to ftrace tracers. May be invoked mutiple times for multiple trace options. For example trace options look at /sys/kernel/debug/tracing/trace_options -p, --prio=PRIO Set the priority of the first thread. The given priority is set to the first test thread. Each further thread gets a lower priority: Priority(Thread N) = max(Priority(Thread N-1) - 1, 0) -q, --quiet Run the tests quiet and print only a summary on exit. Useful for automated tests, where only the summary output needs to be cap- tured. -r, --relative Use relative timers instead of absolute. The default behaviour of the tests is to use absolute timers. This option is there for com- pleteness and should not be used for reproducible tests. -s, --system Use sys_nanosleep and sys_setitimer instead of posix timers. Note, that -s can only be used with one thread because itimers are per process and not per thread. -s in combination with -n uses the nanosleep syscall and is not restricted to one thread. -T, --tracer=TRACEFUNC set the ftrace tracer function. Used with the -b option. Must be one of the trace functions available from <debugfs-mountpoint>/ker- nel/debug/tracing/available_tracers -t, --threads[=NUM] Set the number of test threads (default is 1). Create NUM test threads. If NUM is not specified, NUM is set to the number of avail- able CPUs. See -d, -i and -p for further information. -m, --mlockall Lock current and future memory allocations to prevent being paged out -v, --verbose Output values on stdout for statistics. This option is used to gather statistical information about the latency distribution. The output is sent to stdout. The output format is: n:c:v where n=task number c=count v=latency value in us. Use this option in combination with -l -D, --duration=TIME Run the test for the specified time, which defaults to seconds. Append 'm', 'h', or 'd' to specify minutes, hours or days -w, --wakeup task wakeup tracing (used with -b) -W, --wakeuprt rt-task wakeup tracing (used with -b) -y, --policy=NAME set the scheduler policy of the measurement threads where NAME is one of: other, normal, batch, idle, fifo, rr -M, --refresh_on_max delay updating the screen until a new max latency is hit (useful for running cyclictest on low-bandwidth connections) -S, --smp Set options for standard testing on SMP systems. Equivalent to using the options: "-t -a -n" as well keeping any specified priority equal across all threads -U, --numa Similar to the above --smp option, this implies the "-t -a -n" options, as well as a constant measurement interval, but also forces memory allocations using the numa(3) policy library. Thread stacks and data structures are allocated from the NUMA node local to the core to which the thread is bound. Requires the underlying kernel to have NUMA support compiled in. AUTHOR
cyclictest was written by Thomas Gleixner <tglx@linuxtronix.de>. This manual page was written by Alessio Igor Bogani <abogani@texware.it>, for the Debian project (but may be used by others). december 20, 2007 CYCLICTEST(8)