linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd.schubert-97jfqw80gc6171pxa8y+qA@public.gmane.org>
To: Nikhilesh Reddy <reddyn-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
	torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
	Miklos Szeredi <miklos-sUDqSbJrdHQHWmgEVkV9KA@public.gmane.org>,
	fuse-devel
	<fuse-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org,
	linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org,
	Richard Weinberger
	<richard.weinberger-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Theodore Ts'o <tytso-3s7WtUTddSA@public.gmane.org>,
	jack-AlSwsSmVLrQ@public.gmane.org,
	Antonio SJ Musumeci
	<trapexit-wGTF+nt6ur047o9RxwvyTQ@public.gmane.org>,
	sven.utcke-Mmb7MZpHnFY@public.gmane.org,
	Nikolaus Rath <nikolaus-BTH8mxji4b0@public.gmane.org>,
	Jann Horn <jannhorn-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Subject: Re: [PATCH v4] fuse: Add support for passthrough read/write
Date: Thu, 21 Jan 2016 13:38:32 +0100	[thread overview]
Message-ID: <56A0D148.7080508@fastmail.fm> (raw)
In-Reply-To: <56A0235E.8090205-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>



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-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>

I think it is common style to add a change log between patch set
versions in the patch description.


Bernd

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21  0:16 [PATCH v4] fuse: Add support for passthrough read/write Nikhilesh Reddy
     [not found] ` <56A0235E.8090205-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-01-21 12:38   ` Bernd Schubert [this message]
     [not found]     ` <56A0D148.7080508-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2016-01-21 12:45       ` Richard Weinberger
2016-01-21 17:59         ` Nikhilesh Reddy
2016-01-22 23:04   ` Mike Shal
     [not found]     ` <CA+6x0LUrBHPf7YyNgwoY4c3fxACBpspycM45Tj=XWQ6oKsRK-g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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=56A0D148.7080508@fastmail.fm \
    --to=bernd.schubert-97jfqw80gc6171pxa8y+qa@public.gmane.org \
    --cc=fuse-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
    --cc=jack-AlSwsSmVLrQ@public.gmane.org \
    --cc=jannhorn-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org \
    --cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=miklos-sUDqSbJrdHQHWmgEVkV9KA@public.gmane.org \
    --cc=nikolaus-BTH8mxji4b0@public.gmane.org \
    --cc=reddyn-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
    --cc=richard.weinberger-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=sven.utcke-Mmb7MZpHnFY@public.gmane.org \
    --cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
    --cc=trapexit-wGTF+nt6ur047o9RxwvyTQ@public.gmane.org \
    --cc=tytso-3s7WtUTddSA@public.gmane.org \
    --cc=viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org \
    /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;
as well as URLs for NNTP newsgroup(s).