03-07-2012
This is likely due to hyper-threading. Each core supports two threads reported as separate virtual CPUs.
This User Gave Thanks to jlliagre For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hi,
we all know /proc is about the information of active process,
I have just read an artical which said you can use /proc/cpuinfo,
/proc/net./proc/meminfo etc. to know about some hardware
information .But I want to know how to use with command line? (1 Reply)
Discussion started by: fuqiang1976
1 Replies
2. UNIX for Advanced & Expert Users
Anyone know what the difference between the /proc filesystems under Linux and SunOS?
Thanx In Advance!
-Lola (1 Reply)
Discussion started by: Sparticus007
1 Replies
3. UNIX for Advanced & Expert Users
/proc is filing up my root filesystem. Can you delete any of the4 ID numbers out of /proc. Please help me. (3 Replies)
Discussion started by: aojmoj
3 Replies
4. UNIX for Dummies Questions & Answers
Hi,
What are the various way's to fix /proc folder in redhat linux 7.2 and how to verify /proc folder is proper or croupted?
Thank in advance
Bache Gowda (7 Replies)
Discussion started by: bache_gowda
7 Replies
5. UNIX for Dummies Questions & Answers
Perhaps this is a very dummy question but sorry I don't know other place to do it. We just buy a new cluster of Xeon machines but there is something I don't understand and perhaps someone can help me.
The more /proc/cpuinfo produces the following output (just part of it).
processor : 0... (1 Reply)
Discussion started by: jhc
1 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I am trying to calculate the CPU Usage by getting the difference between the idle time reported by /proc/stat at 2 different intervals. Now the 4th entry in the first line of /proc/stat will give me the 'idle time'. But I also came across /proc/uptime that gives me 2 entries : 1st one as the... (0 Replies)
Discussion started by: coderd
0 Replies
7. UNIX for Dummies Questions & Answers
So, I'm looking over /proc/cpuinfo and have a question... I've read that "siblings" refers to hyperthreading, but that seems odd considering the contents of cpuinfo. Here's a part:
model name : Intel(R) Xeon(R) CPU E5410 @ 2.33GHz
physical id : 0
siblings : 4
core... (1 Reply)
Discussion started by: treesloth
1 Replies
8. UNIX for Dummies Questions & Answers
If you are adding the kernel module without any module parameter passing, it should print out following information to info1 file so that user can make read access to info1 file (via, for example, cat /proc/info1):
• Processor type
• Kernel version
• Total number of the processes currently... (1 Reply)
Discussion started by: shekhar.huded
1 Replies
9. UNIX for Dummies Questions & Answers
Hi everyone,
I am running Debian Wheezy 7.2 with a 3.2.0-4-686-pae kernel. There are a couple of virtual files and directories in /proc I can't seem to find much information about. I am aware that some of them might be legacy, though. Anyway, here they are:
acpi: according to this link, this... (2 Replies)
Discussion started by: gacanepa
2 Replies
10. SuSE
Here is a chance for Linux users to easily compare Linux CPU info and some meaningless BOGOMIPS. Everyone who is running Linux is welcome to:
cat /proc/cpuinfo
and post the results.
Here is the results for www.unix.com:
processor : 0
vendor_id : AuthenticAMD
cpu family... (182 Replies)
Discussion started by: Neo
182 Replies
LEARN ABOUT CENTOS
libpfm_intel_nhm
LIBPFM(3) Linux Programmer's Manual LIBPFM(3)
NAME
libpfm_intel_nhm - support for Intel Nehalem core PMU
SYNOPSIS
#include <perfmon/pfmlib.h>
PMU name: nhm
PMU desc: Intel Nehalem
PMU name: nhm_ex
PMU desc: Intel Nehalem EX
DESCRIPTION
The library supports the Intel Nehalem core PMU. It should be noted that this PMU model only covers the each core's PMU and not the socket
level PMU. It is provided separately. Support is provided for the Intel Core i7 and Core i5 processors.
MODIFIERS
The following modifiers are supported on Intel Nehalem processors:
u Measure at user level which includes privilege levels 1, 2, 3. This corresponds to PFM_PLM3. This is a boolean modifier.
k Measure at kernel level which includes privilege level 0. This corresponds to PFM_PLM0. This is a boolean modifier.
i Invert the meaning of the event. The counter will now count cycles in which the event is not occurring. This is a boolean modifier
e Enable edge detection, i.e., count only when there is a state transition from no occurrence of the event to at least one occurrence.
This modifier must be combined with a counter mask modifier (m) with a value greater or equal to one. This is a boolean modifier.
c Set the counter mask value. The mask acts as a threshold. The counter will count the number of cycles in which the number of occur-
rences of the event is greater or equal to the threshold. This is an integer modifier with values in the range [0:255].
t Measure on both threads at the same time assuming hyper-threading is enabled. This is a boolean modifier.
ldlat Pass a latency threshold to the MEM_INST_RETIRED:LATENCY_ABOVE_THRESHOLD event. This is an integer attribute that must be in the
range [3:65535]. It is required for this event. Note that the event must be used with precise sampling (PEBS).
OFFCORE_RESPONSE event
The library is able to encode the OFFCORE_RESPONSE_0 event. This is a special event because it needs a second MSR (0x1a6) to be programmed
for the event to count properly. Thus two values are necessary. The first value can be programmed on any of the generic counters. The sec-
ond value goes into the dedicated MSR (0x1a6).
The OFFCORE_RESPONSE event is exposed as a normal event with several umasks which are divided in two groups: request and response. The user
must provide at least one umask from each group. For instance, OFFCORE_RESPONSE_0:ANY_DATA:LOCAL_DRAM.
When using pfm_get_event_encoding(), two 64-bit values are returned. The first value corresponds to what needs to be programmed into any of
the generic counters. The second value must be programmed into the dedicated MSR (0x1a6).
When using an OS-specific encoding routine, the way the event is encoded is OS specific. Refer to the corresponding man page for more
information.
AUTHORS
Stephane Eranian <eranian@gmail.com>
September, 2009 LIBPFM(3)