Messages in this thread | | | Date | Sat, 4 Sep 1999 09:44:14 +0200 | From | Matthew Wilcox <> | Subject | Re: /proc/cpuinfo verbiage differ unnecessarily between ports... |
| |
On Fri, Sep 03, 1999 at 12:51:04PM -0500, Mark H. Wood wrote: > There's still a problem though, if I understand sysctl's argument > structure: you can only fetch (or set) one thing at a time. That means > that a monitoring tool could be causing quite a lot of context-switching.
a syscall isn't a context-switch. I remember hearing someone say that mingo has patches to bring it down to 30us. That's not a lot :-)
> A better way would be (say) a sysctln() that would take a whole list of > items and return them all in a single pair of context switches. > (*Setting* N items in one call leads to difficulties with partial success, > so maybe it should be a read-only sysjustshowmen(). :-)
Like readv/writev?
-- Matthew Wilcox <willy@bofh.ai> "Windows and MacOS are products, contrived by engineers in the service of specific companies. Unix, by contrast, is not so much a product as it is a painstakingly compiled oral history of the hacker subculture." - N Stephenson
- 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/
| |