From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nikolaus Rath Subject: Re: [PATCH] fuse: Add support for fuse stacked I/O Date: Fri, 15 Jan 2016 13:38:01 -0800 Message-ID: <87oacm7ccm.fsf@thinkpad.rath.org> References: <565394BE.4040506@codeaurora.org> <5696E366.2080605@codeaurora.org> <20160114045716.GB8006@kroah.com> <5697EF97.9020800@codeaurora.org> <871t9i91e1.fsf@thinkpad.rath.org> <56994884.9060002@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <56994884.9060002-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> (Nikhilesh Reddy's message of "Fri, 15 Jan 2016 11:29:08 -0800") Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Nikhilesh Reddy Cc: Andy Lutomirski , Linus Torvalds , fuse-devel , Al Viro , Greg KH , linux-fsdevel , Linux API , Jan Kara , Theodore Ts'o , sven.utcke-Mmb7MZpHnFY@public.gmane.org, Miklos Szeredi , Richard Weinberger , Linux Kernel Mailing List , Antonio SJ Musumeci List-Id: linux-api@vger.kernel.org On Jan 15 2016, Nikhilesh Reddy wrote: > Our local benchmarks on embedded devices (where power and cpu usage i= s > critical) show that splice doesnt help as much .. when running > multiple cpu's results in increased power usage > > The below results are on a specific device model. > > Where IOPS is number of 4K based read or writes that could be perform= ed each second. > > regular spliced Stac= ked I/O > sequencial write (MiBPS) 56.55633333 100.34445 141.7096667 > sequencial read (MiBPS) 49.644 60.43434 122.36= 7 > > random write (IOPS) 2554.333333 4053.4545 8572 > random read (IOPS) 977.3333333 1223.34 1432.666667 > > The above tests were performed using a file size of 1GB That looks convincing to me. > Also we can called it FUSE_DELEGATED_IO if that helps :). > I chose to call is stacked i/o since we are technically stacking the > fuse read/writes on the ext4/fat or other filesystems. Yeah, but "stacked" has a pretty strong association with union/overlay file systems (as you have seen), and the feature is not at all specific to that usecase. =46or example, many FUSE file systems store data in some remote server over the network but cache it on a local disk. The access to the cached data would benefit from the feature under discussion, but I have a hard time thinking of such a FUSE file system being "stacked" on the file system that happens to hold its cache. Best, -Nikolaus --=20 GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F =46ingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.= =C2=AB