From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: [fuse-devel] [PATCH 4/6] fs/fuse: support compiling out splice Date: Mon, 24 Nov 2014 12:22:14 -0800 Message-ID: <20141124202214.GA11362@kroah.com> References: <1416752468-1626-1-git-send-email-pieter@boesman.nl> <1416752468-1626-5-git-send-email-pieter@boesman.nl> <20141123232302.GA12456@thin> <20141124094931.GA1055@smipidev> <20141124160510.GA2446@jtriplet-mobl1> <20141124193412.GB31618@kroah.com> <20141124201450.GA18776@cloud> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20141124201450.GA18776@cloud> Sender: linux-kernel-owner@vger.kernel.org To: josh@joshtriplett.org Cc: Pieter Smith , Richard Weinberger , "Michael S. Tsirkin" , Bertrand Jacquin , Oleg Nesterov , "J. Bruce Fields" , Eric Dumazet , =?utf-8?B?6JSh5q2j6b6Z?= , Jeff Layton , Tom Herbert , Alexei Starovoitov , Miklos Szeredi , Peter Foley , Hugh Dickins , Xiao Guangrong , Geert Uytterhoeven , Mel Gorman , Matt Turner , "Paul E. McKenney" , Alexander Duyck , "open list:FUSE: FILESYSTEM..." , Luis R. List-Id: linux-api@vger.kernel.org On Mon, Nov 24, 2014 at 12:14:50PM -0800, josh@joshtriplett.org wrote: > > I would, again, argue that stuff like __splice_p() not be implemented at > > all please. It will only cause a huge proliferation of stuff like this > > that will not make any sense, and only cause a trivial, if any, amount > > of code savings. > > > > I thought you were going to not do this type of thing until you got the > > gcc optimizer working for function callbacks. > > Compared to the previous patchset, there are now only two instances of > ifdefs outside of the splice code for this, and this is one of them. In > this case, the issue is no longer about making the code for this > splice_read function disappear, but rather to eliminate a reference to a > bit of splice functionality (used *inside* the FUSE splice code) that > will not work without SPLICE_SYSCALL. > > Would you prefer to see this specific case handled via an #ifdef in > fs/fuse/dev.c rather than introducing a __splice_p that people might be > inclined to propagate? That'd be fine; the code could simply wrap > fuse_dev_splice_read in an #ifdef and have the #else define a NULL > fuse_dev_splice_read. Yes, I would prefer that, but I'm not the fuse maintainer. thanks, greg k-h