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
acpi_hpet
HPET(4) BSD Kernel Interfaces Manual HPET(4)NAME
hpet -- High Precision Event Timer driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device acpi
The following tunables are settable from the loader(8):
hint.hpet.X.allowed_irqs
is a 32bit mask. Each set bit allows driver to use respective IRQ, if BIOS also set respective capability bit in comparator's configuration
register. Default value is 0xffff0000, except some known broken hardware.
hint.hpet.X.clock
controls event timers functionality support. Setting to 0, disables it. Default value is 1.
hint.hpet.X.legacy_route
controls "LegacyReplacement Route" mode. If enabled, HPET will steal IRQ0 of i8254 timer and IRQ8 of RTC. Before using it, make sure that
respective drivers are not using interrupts, by setting also:
hint.attimer.0.clock=0
hint.atrtc.0.clock=0
Default value is 0.
hint.hpet.X.per_cpu
controls how much per-CPU event timers should driver attempt to register. This functionality requires every comparator in a group to have
own unshared IRQ, so it depends on hardware capabilities and interrupts configuration. Default value is 1.
DESCRIPTION
This driver uses High Precision Event Timer hardware (part of the chipset, usually enumerated via ACPI) to supply kernel with one time
counter and several (usually from 3 to 8) event timers. This hardware includes single main counter with known increment frequency (10MHz or
more), and several programmable comparators (optionally with automatic reload feature). When value of the main counter matches current value
of any comparator, interrupt can be generated. Depending on hardware capabilities and configuration, interrupt can be delivered as regular
I/O APIC interrupt (ISA or PCI) in range from 0 to 31, or as Front Side Bus interrupt, alike to PCI MSI interrupts, or in so called "Lega-
cyReplacement Route" HPET can steal IRQ0 of i8254 and IRQ8 of the RTC. Interrupt can be either edge- or level-triggered. In last case they
could be safely shared with PCI IRQs. Driver prefers to use FSB interrupts, if supported, to avoid sharing. If it is not possible, it uses
single sharable IRQ from PCI range. Other modes (LegacyReplacement and ISA IRQs) require special care to setup, but could be configured man-
ually via device hints.
Event timers provided by the driver support both one-shot an periodic modes and irrelevant to CPU power states.
Depending on hardware capabilities and configuration, driver can expose each comparator as separate event timer or group them into one or
several per-CPU event timers. In last case interrupt of every of those comparators within group is bound to specific CPU core. This is possi-
ble only when each of these comparators has own unsharable IRQ.
SEE ALSO acpi(4), apic(4), atrtc(4), attimer(4), eventtimers(4), timecounters(4)HISTORY
The hpet driver first appeared in FreeBSD 6.3. Support for event timers was added in FreeBSD 9.0.
BSD September 14, 2010 BSD