@@ -5,7 +5,7 @@# Rewritten to use lists instead of if-statements.# -obj-y:=open.oread_write.osendfile.ofile_table.osuper.o\+obj-y:=open.oread_write.ofile_table.osuper.o\char_dev.ostat.oexec.opipe.onamei.ofcntl.o\ioctl.oreaddir.oselect.odcache.oinode.o\attr.obad_inode.ofile.ofilesystems.onamespace.o\
On Mon, Oct 20, 2014 at 11:48:37PM +0200, Pieter Smith wrote:
Many embedded systems will not need this syscall, and omitting it
saves space. Add a new EXPERT config option CONFIG_SENDFILE_SYSCALL
(default y) to support compiling it out.
Nice work, thanks!
If there are no objections, and nobody has a tree they'd rather carry
this through, I'll take the series through the tiny tree when it's ready
to merge.
Interesting inlining decisions by GCC here. Got a bloat-o-meter for the
two-patch series, by any chance? (Also, is this with tinyconfig? In
particular, with OPTIMIZE_INLINING and OPTIMIZE_FOR_SIZE?) I'm
wondering if moving sendfile to a separate file made GCC put fdput
out-of-line, and compiling it out reversed that again.
@@ -5,7 +5,7 @@# Rewritten to use lists instead of if-statements.# -obj-y:=open.oread_write.osendfile.ofile_table.osuper.o\+obj-y:=open.oread_write.ofile_table.osuper.o\char_dev.ostat.oexec.opipe.onamei.ofcntl.o\ioctl.oreaddir.oselect.odcache.oinode.o\attr.obad_inode.ofile.ofilesystems.onamespace.o\
I'm thinking of adding a submenu to group config FOO_SYSCALL options. :)
I'll probably push that as part of the 3.19 merge window, as a patch on
top of all of the individual tinification options.
quoted hunk
config PCI_QUIRKS
default y
bool "Enable PCI quirk workarounds" if EXPERT
From: Christoph Hellwig <hidden> Date: 2014-10-21 07:51:54
On Mon, Oct 20, 2014 at 03:24:22PM -0700, josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org wrote:
On Mon, Oct 20, 2014 at 11:48:37PM +0200, Pieter Smith wrote:
quoted
Many embedded systems will not need this syscall, and omitting it
saves space. Add a new EXPERT config option CONFIG_SENDFILE_SYSCALL
(default y) to support compiling it out.
Nice work, thanks!
If there are no objections, and nobody has a tree they'd rather carry
this through, I'll take the series through the tiny tree when it's ready
to merge.
I think it's rather pointless - there is very little sendfile code,
so you'd rather want to disable splice.
On Tue, Oct 21, 2014 at 12:51:54AM -0700, Christoph Hellwig wrote:
On Mon, Oct 20, 2014 at 03:24:22PM -0700, josh@joshtriplett.org wrote:
quoted
On Mon, Oct 20, 2014 at 11:48:37PM +0200, Pieter Smith wrote:
quoted
Many embedded systems will not need this syscall, and omitting it
saves space. Add a new EXPERT config option CONFIG_SENDFILE_SYSCALL
(default y) to support compiling it out.
Nice work, thanks!
If there are no objections, and nobody has a tree they'd rather carry
this through, I'll take the series through the tiny tree when it's ready
to merge.
I think it's rather pointless - there is very little sendfile code,
so you'd rather want to disable splice.
That's the plan, but since sendfile depends on some of the splice bits,
sendfile needs to be optional as well; SENDFILE_SYSCALL will then select
SPLICE_SYSCALLS.
- Josh Triplett
From: Christoph Hellwig <hch@infradead.org> Date: 2014-10-21 09:13:56
On Tue, Oct 21, 2014 at 02:04:22AM -0700, Josh Triplett wrote:
That's the plan, but since sendfile depends on some of the splice bits,
sendfile needs to be optional as well; SENDFILE_SYSCALL will then select
SPLICE_SYSCALLS.
Just include sendfile with the splice syscalls - we don't really need a
config option for every obscure syscall.
On Tue, Oct 21, 2014 at 02:13:56AM -0700, Christoph Hellwig wrote:
On Tue, Oct 21, 2014 at 02:04:22AM -0700, Josh Triplett wrote:
quoted
That's the plan, but since sendfile depends on some of the splice bits,
sendfile needs to be optional as well; SENDFILE_SYSCALL will then select
SPLICE_SYSCALLS.
Just include sendfile with the splice syscalls - we don't really need a
config option for every obscure syscall.
No objection here. Pieter, since you're planning to remove splice
anyway, can you just fold the two together under the same Kconfig
option? That should simplify the patch series, since you won't need to
split the two.
- Josh Triplett