Sponsored Content
Full Discussion: CPU Count
Operating Systems Linux Red Hat CPU Count Post 302595204 by Corona688 on Thursday 2nd of February 2012 10:57:34 AM
Old 02-02-2012
It could mean one 8-core CPU, a pair of 4-core CPU's, four 2-core CPU's, or 8 1-core CPU's. Cores are counted individually. If you care which belongs in what chip, that's the physical ID.

If you just care about the number of cores, counting the line match like that will work fine.

In fact, you don't need to even match anything. Just count the number of records, splitting on blank lines, by setting RS to "". Then when awk runs out of input, print NR, the number of records. On my dual-core system:

Code:
$ awk -v RS="" 'END { print NR }' /proc/cpuinfo
2
$

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

CPU count

Is there an easy way in Solaris to count the number of processors? (2 Replies)
Discussion started by: hshapiro
2 Replies

2. UNIX for Dummies Questions & Answers

how to get persistant cpu utilization values per process per cpu in linux (! top,ps)

hi, i want to know cpu utilizatiion per process per cpu..for single processor also if multicore in linux ..to use these values in shell script to kill processes exceeding cpu utilization.ps (pcpu) command does not give exact values..top does not give persistant values..psstat,vmstat..does njot... (3 Replies)
Discussion started by: pankajd
3 Replies

3. Solaris

Multi CPU Solaris system shows 100% CPU usage.

Hello Friends, On one of my Solaris 10 box, CPU usage shows 100% using "sar", "vmstat". However, it has 4 CPUs and prstat and glance are not showing enough processes to justify high CPU utilization. ========================================================================= $ prstat -a ... (4 Replies)
Discussion started by: mahive
4 Replies

4. Solaris

cpu-shares vs cpu-cap in solaris

Can anyone tell me difference between cpu-shares vs cpu-cap in solaris & how FSS will work with cpu-caps ? (9 Replies)
Discussion started by: fugitive
9 Replies

5. UNIX for Dummies Questions & Answers

virtualization (VCPU count according to CPU)

We have purchased four intels xeon processors Intel® Xeon® Processor E7530 (12M Cache, 1.86 GHz, 5.86 GT/s Intel® QPI) with SPEC Code(s) SLBRJ As per the specification each cpu has 6 cores therefore we have 24 cores (considering 4 cpus). Now how would i calculate the number of vcpus that can... (1 Reply)
Discussion started by: pinga123
1 Replies

6. AIX

topas and mpstat disagree on CPU count

I have a number of LPARs on one P520. All LPARs are running 5.3 and I observe the following: On some LPARs the number of CPUs found do not match between topas and mpstat. Server 1: $ mpstat System configuration: lcpu=4 ent=0.2 mode=Uncapped cpu min maj mpc int cs ics rq ... (1 Reply)
Discussion started by: petervg
1 Replies

7. Red Hat

finding CPU count - reading sysinfo output

Hello, sysinfo throws out below 3 CPU counts. Can anyone help me understand what each of these means? CPU Count Socketed is 2 CPU Count Physical is 8 CPU Count Virtual is 16 First one seems obvious. However, I wonder how there can be 8 Physical CPUs, if... (2 Replies)
Discussion started by: hnhegde
2 Replies

8. UNIX for Dummies Questions & Answers

Is it possible to combine multiple CPU to act as a single CPU on the same server?

We have a single threaded application which is restricted by CPU usage even though there are multiple CPUs on the server, hence leading to significant performance issues. Is it possible to merge / combine multiple CPUs at OS level so it appear as a single CPU for the application? (6 Replies)
Discussion started by: Dissa
6 Replies

9. AIX

Topas - CPU count inconsistent across LPARs

seeing weirdness across some 7.1.5.1 LPARs - they all have 2 vCPUs allocated shared. With prtconf they show 2 CPUs, 'lsdev -c processor' concurs, and 'lsattr -El procX' shows that SMT is enabled and there are 2 SMT threads (power5, sorry). Yet running topas on them shows 2 CPUs on some and 4 on... (3 Replies)
Discussion started by: maraixadm
3 Replies

10. UNIX for Beginners Questions & Answers

Why Entitlement CPU can't be set to same as Virtual CPU?

I read that Entitlement CPU should be set to max 75% compare to Virtual CPU. May I know the reason. I have set the Entitlement CPU = Virtual CPU on AIX . It works fine . Can you help to understand. (1 Reply)
Discussion started by: gabhanes
1 Replies
HWLOC-CALC(1)							       hwloc							     HWLOC-CALC(1)

NAME
hwloc-calc - Operate on cpu mask strings and objects SYNOPSIS
hwloc-calc [options] <location1> [<location2> [...] ] OPTIONS
-p --physical Use OS/physical indexes instead of logical indexes for both input and output. -l --logical Use logical indexes instead of physical/OS indexes for both input and output (default). --pi --physical-input Use OS/physical indexes instead of logical indexes for input. --li --logical-input Use logical indexes instead of physical/OS indexes for input (default). --po --physical-input Use OS/physical indexes instead of logical indexes for output. --lo --logical-output Use logical indexes instead of physical/OS indexes for output (default). -N --number-of <type|depth> Report the number of objects of the given type or depth that intersect the CPU set. This is convenient for finding how many cores, NUMA nodes or PUs are available in a machine. -I --intersect <type|depth> Find the list of objects of the given type or depth that intersect the CPU set and report the comma-separated list of their indexes instead of the cpu mask string. This may be used for determining the list of objects above or below the input objects. When combined with --physical, the list is convenient to pass to external tools such as taskset or numactl --physcpubind or --membind. This is different from --largest since the latter requires that all reported objects are strictly included inside the input objects. -H --hierarchical <type1>.<type2>... Find the list of objects of type <type2> that intersect the CPU set and report the space-separated list of their hierarchical indexes with respect to <type1>, <type2>, etc. For instance, if socket.core is given, the output would be Socket:1.Core:2 Socket:2.Core:3 if the input contains the third core of the second socket and the fourth core of the third socket. --largest Report (in a human readable format) the list of largest objects which exactly include all input objects. None of these output objects intersect each other, and the sum of them is exactly equivalent to the input. No largest object is included in the input This is different from --intersect where reported objects may not be strictly included in the input. --sep <sep> Change the field separator in the output. By default, a space is used to separate output objects (for instance when --hierarchi- cal or --largest is given) while a comma is used to separate indexes (for instance when --intersect is given). --single Singlify the output to a single CPU. --taskset Display CPU set strings in the format recognized by the taskset command-line program instead of hwloc-specific CPU set string format. This option has no impact on the format of input CPU set strings, both formats are always accepted. --restrict <cpuset> Restrict the topology to the given cpuset. -i <file>, --input <file> Read topology from XML file <file> (instead of discovering the topology on the local machine). If <file> is "-", the standard input is used. XML support must have been compiled in to hwloc for this option to be usable. -i <directory>, --input <directory> Read topology from the chroot specified by <directory> (instead of discovering the topology on the local machine). This option is generally only available on Linux. The chroot was usually created by gathering another machine topology with hwloc-gather- topology. -i <specification>, --input <specification> Simulate a fake hierarchy (instead of discovering the topology on the local machine). If <specification> is "node:2 pu:3", the topology will contain two NUMA nodes with 3 processing units in each of them. The <specification> string must end with a number of PUs. --if <format>, --input-format <format> Enforce the input in the given format, among xml, fsroot and synthetic. -v Verbose output. --version Report version and exit. DESCRIPTION
hwloc-calc generates and manipulates CPU mask strings or objects. Both input and output may be either objects (with physical or logical indexes), CPU lists (with physical or logical indexes), or CPU mask strings (always physically indexed). If objects or CPU mask strings are given on the command-line, they are combined and a single output is printed. If no object or CPU mask strings are given on the command-line, the program will read the standard input. It will combine multiple objects or CPU mask strings that are given on the same line of the standard input line with spaces as separators. Different input lines will be processed separately. Command-line arguments and options are processed in order. For instance, it means that changing the type of input indexes with --li or changing the input topology with -i only affects the processing the following arguments. NOTE: It is highly recommended that you read the hwloc(7) overview page before reading this man page. Most of the concepts described in hwloc(7) directly apply to the hwloc-calc utility. EXAMPLES
hwloc-calc's operation is best described through several examples. To display the (physical) CPU mask corresponding to the second socket: $ hwloc-calc socket:1 0x000000f0 To display the (physical) CPU mask corresponding to the third socket, excluding its even numbered logical processors: $ hwloc-calc socket:2 ~PU:even 0x00000c00 To combine two (physical) CPU masks: $ hwloc-calc 0x0000ffff 0xff000000 0xff00ffff To display the list of logical numbers of processors included in the second socket: $ hwloc-calc --intersect PU socket:1 4,5,6,7 To bind GNU OpenMP threads logically over the whole machine, we need to use physical number output instead: $ export GOMP_CPU_AFFINITY=`hwloc-calc --physical --intersect PU machine:0` $ echo $GOMP_CPU_AFFINITY 0,2,1,3 To display the list of NUMA nodes, by physical indexes, that intersect a given (physical) CPU mask: $ hwloc-calc --physical --intersect NUMAnode 0xf0f0f0f0 0,2 To display the physical index of a processor given by its logical index: $ hwloc-calc PU:2 --physical-output --intersect PU 3 To display the set of CPUs near network interface eth0: $ hwloc-calc os=eth0 0x00005555 To display the indexes of sockets near PCI device whose bus ID is 0000:01:02.0: $ hwloc-calc pci=0000:01:02.0 --intersect Socket 1 To display the list of per-socket cores that intersect the input: $ hwloc-calc 0x00003c00 --hierarchical socket.core Socket:2.Core:1 Socket:3.Core:0 To display the (physical) CPU mask of the entire topology except the third socket: $ hwloc-calc all ~socket:3 0x0000f0ff To combine both physical and logical indexes as input: $ hwloc-calc PU:2 --physical-input PU:3 0x0000000c To synthetize a set of cores into largest objects on a 2-node 2-socket 2-core machine: $ hwloc-calc core:0 --largest Core:0 $ hwloc-calc core:0-1 --largest Socket:0 $ hwloc-calc core:4-7 --largest NUMANode:1 $ hwloc-calc core:2-6 --largest Socket:1 Socket:2 Core:6 $ hwloc-calc socket:2 --largest Socket:2 $ hwloc-calc socket:2-3 --largest NUMANode:1 To get the set of first threads of all cores: $ hwloc-calc core:all.pu:0 RETURN VALUE
Upon successful execution, hwloc-calc displays the (physical) CPU mask string, (physical or logical) object list, or (physical or logical) object number list. The return value is 0. hwloc-calc will return nonzero if any kind of error occurs, such as (but not limited to): failure to parse the command line. SEE ALSO
hwloc(7), hwloc-gather-topology(1) 1.4.1 Feb 27, 2012 HWLOC-CALC(1)
All times are GMT -4. The time now is 04:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy