PCI: Unable to handle 64-bit address space for
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 handle 64-bit address space for PCI: Unable to handle 64-bit address space for PCI: Unable to handle 64-bit address space for PCI: Unable to handle 64-bit address space for PCI: Unable to handle 64-bit address space for PCI: Unable to handle 64-bit address space for PCI: Unable to handle 64-bit address space for PCI: Unable to handle 64-bit address space for Thanks for the help, Michael - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
PCI: Unable to handle 64-bit address space for
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 handle 64-bit address space for PCI: Unable to handle 64-bit address space for PCI: Unable to handle 64-bit address space for PCI: Unable to handle 64-bit address space for PCI: Unable to handle 64-bit address space for PCI: Unable to handle 64-bit address space for PCI: Unable to handle 64-bit address space for PCI: Unable to handle 64-bit address space for Thanks for the help, Michael - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Cheap lock for user mode processes release when process exits
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 futex on 2.6.9-42.EL. However, if one of the processes is killed/exits, the lock doesn't get released. I can trap the signal to release the lock, but not all signals like kill. Anyway I can achieve this without a potential deadlock? Thanks, Michael - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Cheap lock for user mode processes release when process exits
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 futex on 2.6.9-42.EL. However, if one of the processes is killed/exits, the lock doesn't get released. I can trap the signal to release the lock, but not all signals like kill. Anyway I can achieve this without a potential deadlock? Thanks, Michael - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Any faster and more efficient way to repeatedly access /proc/*
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
way to manage.
Imagine, having to probe the stat of each process?
Thanks,
Michael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Any faster and more efficient way to repeatedly access /proc/*
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 way to manage. Imagine, having to probe the stat of each process? Thanks, Michael - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
