lkml.org 
[lkml]   [1999]   [Sep]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: /proc/cpuinfo verbiage differ unnecessarily between ports...
From
Date
>>>>> "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/

\
 
 \ /
  Last update: 2005-03-22 13:53    [W:0.043 / U:0.188 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site