Hi all,
Anyone has idea of this: Why it is displayed on boot? How to fix this? Or at
least not to display this message?
Using 2.6.9-42.ELsmp.
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDE controller :00:1f.1
PCI: Unable to handle 64-bit address space for
PCI: Unable to
Hi all,
Anyone has idea of this: Why it is displayed on boot? How to fix this? Or at
least not to display this message?
Using 2.6.9-42.ELsmp.
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDE controller :00:1f.1
PCI: Unable to handle 64-bit address space for
PCI: Unable to
Hi all,
Maybe someone here knows better.
I have several user-mode processes using shared mmap. There can be several
reader processes and only one writer. Readers access the shared region
frequently, writer seldom.
Naturally, multi-reader/single-writer locks works best. I tried this with
Hi all,
Maybe someone here knows better.
I have several user-mode processes using shared mmap. There can be several
reader processes and only one writer. Readers access the shared region
frequently, writer seldom.
Naturally, multi-reader/single-writer locks works best. I tried this with
Hi,
Is there a faster way to access "/proc/*" other than open it as a file and
reading/parsing contents? e.g. fopen("/proc/stat", "r");
In BSD, there is the kvm method of access, which is relatively fast (light
weight)
In Linux, if I have a daemon that keeps track of these statistics, it's a
Hi,
Is there a faster way to access /proc/* other than open it as a file and
reading/parsing contents? e.g. fopen(/proc/stat, r);
In BSD, there is the kvm method of access, which is relatively fast (light
weight)
In Linux, if I have a daemon that keeps track of these statistics, it's a hell
6 matches
Mail list logo
