[Please don't top-post.] On Sun, Nov 16, 2014 at 01:18:27PM +0100, Pieter Smith wrote: > I had a look at the numbers (see below): For a tinyconfig kernel, savings > outside fs/splice.c are negligible. With the addition of networking > however, net/core and net/ipv4 can be squeezed for usable savings. > > Should I leave networking (and the rest) until we can come up with a > non-icky approach outside fs/splice.c? > > *THE NUMBERS* > > Given a tinyconfig, fs/splice.c can free up 8.2K (3.5K + 4.7K) with > CONFIG_SYSCALL_SPLICE. The rest are not worth the effort: > fs/splice: > syscalls only: add/remove: 0/16 grow/shrink: 2/5 up/down: 114/-3693 > (-3579) > the remainder: add/remove: 0/24 grow/shrink: 0/4 up/down: 0/-4824 > (-4824)
Nice! Go ahead and submit the patches for that portion, and the rest can wait until we get compiler support for omitting structure fields. - Josh Triplett -- 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/
