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)
I did a search on this, but didn't find exactly the answer I'm looking for. What exactly is the proc directory for? Showing processes spawned by users? I ask because I have some very large files in that directory by multiple users and its affecting my disk usage. Can you limit how many... (2 Replies)
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)
:)
hi all !
Please help me
When I select data from oracle with proc * C prog.
I count the number of rows
For example the total rows is 1000000
but the number of result return is a limit number 5000 for ex
So How can I know this limit (5 Replies)
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)
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)
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)
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)
Hi,
I wanted to understand what exactly /proc/cpuinfo shows?
We have a machine with following specification...
(2x) Intel Xeon 6-core processors
So, ideally it shouls have 12processors, but the output on /proc/cpuinfo shows 24 processors.
Can someone please explain how this is... (3 Replies)
Discussion started by: shrshah64
3 Replies
LEARN ABOUT FREEBSD
timecounters
TIMECOUNTERS(4) BSD Kernel Interfaces Manual TIMECOUNTERS(4)NAME
timecounters -- kernel time counters subsystem
SYNOPSIS
The kernel uses several types of time-related devices, such as: real time clocks, time counters and event timers. Real time clocks are
responsible for tracking real world time, mostly when the system is down. Time counters are responsible for tracking purposes, when the sys-
tem is running. Event timers are responsible for generating interrupts at a specified time or periodically, to run different time-based
events. This page is about the second.
DESCRIPTION
Time counters are the lowest level of time tracking in the kernel. They provide monotonically increasing timestamps with known width and
update frequency. They can overflow, drift, etc and so in raw form can be used only in very limited performance-critical places like the
process scheduler.
More usable time is created by scaling the values read from the selected time counter and combining it with some offset, regularly updated by
tc_windup() on hardclock() invocation.
Different platforms provide different kinds of timer hardware. The goal of the time counters subsystem is to provide a unified way to access
that hardware.
Each driver implementing time counters registers them with the subsystem. It is possible to see the list of present time counters, via the
kern.timecounter sysctl(8) variable:
kern.timecounter.choice: TSC-low(-100) HPET(950)i8254(0)ACPI-fast(900) dummy(-1000000)
kern.timecounter.tc.ACPI-fast.mask: 16777215
kern.timecounter.tc.ACPI-fast.counter: 13467909
kern.timecounter.tc.ACPI-fast.frequency: 3579545
kern.timecounter.tc.ACPI-fast.quality: 900
kern.timecounter.tc.i8254.mask: 65535
kern.timecounter.tc.i8254.counter: 62692
kern.timecounter.tc.i8254.frequency: 1193182
kern.timecounter.tc.i8254.quality: 0
kern.timecounter.tc.HPET.mask: 4294967295
kern.timecounter.tc.HPET.counter: 3013495652
kern.timecounter.tc.HPET.frequency: 14318180
kern.timecounter.tc.HPET.quality: 950
kern.timecounter.tc.TSC-low.mask: 4294967295
kern.timecounter.tc.TSC-low.counter: 4067509463
kern.timecounter.tc.TSC-low.frequency: 11458556
kern.timecounter.tc.TSC-low.quality: -100
The output nodes are defined as follows:
kern.timecounter.tc.X.mask is a bitmask, defining valid counter bits,
kern.timecounter.tc.X.counter is a present counter value,
kern.timecounter.tc.X.frequency is a counter update frequency,
kern.timecounter.tc.X.quality is an integral value, defining the quality of this time counter compared to others. A negative value means
this time counter is broken and should not be used.
The time management code of the kernel chooses one time counter from that list. The current choice can be read and affected via the
kern.timecounter.hardware tunable/sysctl.
SEE ALSO attimer(4), eventtimers(4), ffclock(4), hpet(4)BSD April 12, 2014 BSD