Messages in this thread | | | Subject | Re: /proc/cpuinfo verbiage differ unnecessarily between ports... | From | Jes Sorensen <> | Date | 03 Sep 1999 09:33:30 +0200 |
| |
>>>>> "Glen" == Glen Turner <glen.turner@adelaide.edu.au> writes:
Glen> As the author of some SNMP code, I'd like to see the *whole* of Glen> /proc adopt a consistent, simple to parse, simple to read, Glen> simple to write structure.
Actually for this you'd want a simple sructured kernel interface, maybe via syscall, to get this information out of the kernel rather than having your user space tool parse /proc. Having the kernel generate ascii strings, then copying these to user space just to have the user space application reparse them in the end is pretty expensive when all you really want is to read an integer value or two.
Once you start cranking up the sample frequency the monitoring can actually start affecting the system load.
Jes
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |