Re: why doesn't x86_32 have the accept4() syscall?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



David Miller wrote:
> Because accept4() has been provided via the sys_socketcall() indirect
> operation, for this socket system call and several others the native
> direct syscalls were never added to the x86 32-bit table and probably
> never will be.

Hi David,

Is there any reason why it was added via sys_socketcall() - isn't that
just a waste of a few cycles and kernel size, compared with a direct
pointer in the syscall table?

I see sendmmsg() and recvmmsg() got proper syscall slots on x86
32-bit, and are in sys_socketcall() as well, which seems a bit pointless.

Thanks,
-- Jamie
--
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel]     [Kernel Newbies]     [x86 Platform Driver]     [Netdev]     [Linux Wireless]     [Netfilter]     [Bugtraq]     [Linux Filesystems]     [Yosemite Discussion]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]

  Powered by Linux