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

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

 



From: Jamie Lokier <jamie@xxxxxxxxxxxxx>
Date: Tue, 10 Jan 2012 16:03:17 +0000

> 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?

Looks like an oversight, but one for which I don't think is worth
correcting.
--
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