From: Christoph Hellwig <hch@infradead.org>
To: Nikhilesh Reddy <reddyn@codeaurora.org>
Cc: 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, torvalds@linux-foundation.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>
Subject: Re: [PATCH] fuse: Add support for fuse stacked I/O
Date: Thu, 14 Jan 2016 00:25:54 -0800 [thread overview]
Message-ID: <20160114082554.GA12489@infradead.org> (raw)
In-Reply-To: <5696E366.2080605@codeaurora.org>
On Wed, Jan 13, 2016 at 03:53:10PM -0800, Nikhilesh Reddy wrote:
> Add support for filesystem stacked read/write of files
> when enabled through a userspace init option of FUSE_STACKED_IO.
>
> When FUSE_STACKED_IO is enabled all the reads and writes
> to the fuse mount point go directly to the native filesystem
> rather than through the fuse daemon. All requests that aren't
> read/write still go thought the userspace code.
Please write your stacked features as kernel drivers.
next prev parent reply other threads:[~2016-01-14 8:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <565394BE.4040506@codeaurora.org>
2016-01-13 23:53 ` [PATCH] fuse: Add support for fuse stacked I/O Nikhilesh Reddy
2016-01-14 4:57 ` Greg KH
2016-01-14 18:57 ` Nikhilesh Reddy
2016-01-14 19:19 ` Linus Torvalds
2016-01-15 16:31 ` Andy Lutomirski
[not found] ` <CALCETrWNQ9ytw1bCOOjFJRstauYc6DocQAmZCF61CErAJ5BF2g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-15 17:37 ` Antonio SJ Musumeci
2016-01-15 17:51 ` Nikolaus Rath
2016-01-15 19:29 ` Nikhilesh Reddy
2016-01-15 21:38 ` Nikolaus Rath
2016-01-15 21:43 ` Linus Torvalds
2016-01-15 21:46 ` Andy Lutomirski
2016-01-15 21:53 ` Linus Torvalds
2016-01-19 2:57 ` Nikhilesh Reddy
2016-01-20 23:24 ` Nikhilesh Reddy
2016-01-15 21:56 ` [fuse-devel] " Hans Beckerus
2016-01-14 8:25 ` Christoph Hellwig [this message]
2016-01-14 15:52 ` Nikolaus Rath
2016-01-15 9:29 ` Christoph Hellwig
2016-01-19 3:07 ` Jann Horn
2016-01-20 23:07 ` 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=20160114082554.GA12489@infradead.org \
--to=hch@infradead.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).