Andi Kleen writes:
On Thursday 13 July 2006 01:24, Theodore Tso wrote:
P.S. I happen to be one those developers who think the binary
interface is not so bad, and for compared to reading from /proc/sys,
the sysctl syscall *is* faster. But at the same there, there really
isn't anything where really does require that kind of speed, so that
point is moot. But at the same time, what is the cost of leaving
sys_sysctl in the kernel for an extra 6-12 months, or even longer,
starting from now?
The numerical namespace for sysctl is unsalvagable imho. e.g.
distributions regularly break it because there is no central
repository of numbers so it's not very usable anyways in practice.
Huh? How exactly is this different from system call numbers,
ioctl numbers, fcntl numbers, ptrace command numbers, and every
other part of the Linux ABI?
Normal sysctl works very well for FreeBSD. I'm jealous.
They also have a few related calls that are very nice.
Here we fight over a few CPU cycles in the syscall entry path,
then piss away performance by requiring open-read-close and
marshalling everything through decimal ASCII text. WTF? Let's
just have one system call (make_XML_SOAP_request) and be done.
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
