Messages in this thread | | | Date | Mon, 16 May 2011 18:01:14 +0200 | From | Andi Kleen <> | Subject | Re: [PATCH 4/5] Add a sysconf syscall |
| |
> ...and libc will start making many such calls in a row in order to retrieve > a dozen of such values.
It doesn't because the user interface is sysconf(). So the user program just asks for it piece by piece.
> It's rather inefficient to return just one word. > Try to return more data per call.
I considered that, but is there a concrete use case? I didn't want to code it up without concrete use case.
> Pass a pointer to the result struct and its length. > Future-proof API, such as using generously wide data types, > passing "version of struct" input parameter to facilitate incompatible > future changes, etc.
Please provide a use case for all this complexity.
[... more complexity snipped ... ]
-Andi
| |