mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Bernd Schubert <bernd.schubert@fastmail.fm>,
	Nikhilesh Reddy <reddyn@codeaurora.org>,
	torvalds@linux-foundation.org, Miklos Szeredi <miklos@szeredi.hu>,
	fuse-devel <fuse-devel@lists.sourceforge.net>,
	linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
	gregkh@linuxfoundation.org, linux-fsdevel@vger.kernel.org,
	viro@zeniv.linux.org.uk,
	Richard Weinberger <richard.weinberger@gmail.com>,
	"Theodore Ts'o" <tytso@mit.edu>,
	jack@suse.cz, Antonio SJ Musumeci <trapexit@spawn.link>,
	sven.utcke@gmx.de, Nikolaus Rath <nikolaus@rath.org>,
	Jann Horn <jannhorn@googlemail.com>
Subject: Re: [PATCH v4] fuse: Add support for passthrough read/write
Date: Thu, 21 Jan 2016 13:45:44 +0100	[thread overview]
Message-ID: <56A0D2F8.4020004@nod.at> (raw)
In-Reply-To: <56A0D148.7080508@fastmail.fm>

Am 21.01.2016 um 13:38 schrieb Bernd Schubert:
> On 01/21/2016 01:16 AM, Nikhilesh Reddy wrote:
>> Add support for filesystem passthrough read/write of files
>> when enabled in userspace through the option FUSE_PASSTHROUGH.
>>
>> There are many FUSE based filesystems that perform checks or
>> enforce policy or perform some kind of decision making in certain
>> functions like the "open" call but simply act as a "passthrough"
>> when performing operations such as read or write.
>>
>> When FUSE_PASSTHROUGH is enabled all the reads and writes
>> to the fuse mount point go directly to the passthrough filesystem
>> i.e a native filesystem that actually hosts the files rather than
>> through the fuse daemon. All requests that aren't read/write still
>> go thought the userspace code.
>>
>> This allows for significantly better performance on read and writes.
>> The difference in performance between fuse and the native lower
>> filesystem is negligible.
>>
>> There is also a significant cpu/power savings that is achieved which
>> is really important on embedded systems that use fuse for I/O.
>>
>> Signed-off-by: Nikhilesh Reddy <reddyn@codeaurora.org>
> 
> I think it is common style to add a change log between patch set
> versions in the patch description.

And please slow down a bit. Collect a few review comments and then
do another version of your patch. :-)

Thanks,
//richard

  reply	other threads:[~2016-01-21 12:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21  0:16 Nikhilesh Reddy
2016-01-21 12:38 ` Bernd Schubert
2016-01-21 12:45   ` Richard Weinberger [this message]
2016-01-21 17:59     ` Nikhilesh Reddy
     [not found] ` <CA+6x0LUrBHPf7YyNgwoY4c3fxACBpspycM45Tj=XWQ6oKsRK-g@mail.gmail.com>
2016-01-25 20:49   ` [fuse-devel] " Nikhilesh Reddy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56A0D2F8.4020004@nod.at \
    --to=richard@nod.at \
    --cc=bernd.schubert@fastmail.fm \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jack@suse.cz \
    --cc=jannhorn@googlemail.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=nikolaus@rath.org \
    --cc=reddyn@codeaurora.org \
    --cc=richard.weinberger@gmail.com \
    --cc=sven.utcke@gmx.de \
    --cc=torvalds@linux-foundation.org \
    --cc=trapexit@spawn.link \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome