On Tue, Nov 25, 2014 at 02:04:41PM -0500, David Miller wrote: > From: j...@joshtriplett.org > Date: Tue, 25 Nov 2014 10:53:10 -0800 > > > It's not a "slippery slope"; it's been our standard practice for ages. > > We've never put an entire class of generic system calls behind > a config option.
I would have loved to make them optional individually, but they all are semantic variations of the same thing: Moving data between fd's without that data passing through userspace. It therefore isn't surprising that these syscalls share an underlying entanglement of code (which is where the bulk of the space saving is to be had). What a tiny product developer should be asking himself, is: "Do I really need to efficiently move data between file descriptors?". If the answer no, he can disable CONFIG_SYSCALL_SPLICE to squeeze an extra 8KB out of his kernel. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
