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 FREEBSD
sched_4bsd
SCHED_4BSD(4) BSD Kernel Interfaces Manual SCHED_4BSD(4)
NAME
sched_4bsd -- 4.4BSD scheduler
SYNOPSIS
options SCHED_4BSD
DESCRIPTION
The sched_4bsd scheduler is the traditional system scheduler, providing both high throughput and solid interactive response in the presence
of load.
The following sysctls are relevant to the operation of sched_4bsd:
kern.sched.name
This read-only sysctl reports the name of the active scheduler.
kern.sched.quantum
This read-write sysctl reports or sets the length of the quantum (in micro-seconds) granted to a thread.
kern.sched.ipiwakeup.enabled
This read-write sysctl sets whether or not the scheduler will generate an inter-processor interrupt (IPI) to an idle CPU when a
thread is woken up. Otherwise, idle CPUs will wait until the next clock tick before looking for new work.
kern.sched.preemption
This read-only sysctl reports whether or not the kernel is configured to support preemption, which reduces the latency to run lower
priority threads on wakeup.
Some sysctls will be available only on systems supporting SMP.
SEE ALSO
sched_ule(4), sysctl(8)
HISTORY
The sched_4bsd scheduler has been present, in various forms, since the inception of BSD.
BUGS
While a highly robust and time-tested scheduler, sched_4bsd lacks specific knowledge of how to schedule advantageously in non-symmetric pro-
cessor configurations, such as hyper-threading.
BSD
January 21, 2008 BSD