From: Nikolaus Rath <Nikolaus@rath.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Nikhilesh Reddy <reddyn@codeaurora.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, 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
Subject: Re: [PATCH] fuse: Add support for fuse stacked I/O
Date: Thu, 14 Jan 2016 07:52:00 -0800 [thread overview]
Message-ID: <87mvs8qhun.fsf@thinkpad.rath.org> (raw)
In-Reply-To: <20160114082554.GA12489@infradead.org> (Christoph Hellwig's message of "Thu, 14 Jan 2016 00:25:54 -0800")
On Jan 14 2016, Christoph Hellwig <hch@infradead.org> wrote:
> 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.
Could you explain in more detail? I think I don't understand either the
why, the how, or what you mean with driver in this context (not sure
which one it is).
(I'm not the original submitter but interested in this)
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
next prev parent reply other threads:[~2016-01-14 15:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <565394BE.4040506@codeaurora.org>
[not found] ` <565394BE.4040506-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.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
[not found] ` <5697EF97.9020800-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-01-14 19:19 ` Linus Torvalds
[not found] ` <CA+55aFwxaU0Y_UxyKFv6WaYsPWDDzZG-rhVtMuLSPcJ0WLLw2A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-15 16:31 ` Andy Lutomirski
[not found] ` <CALCETrWNQ9ytw1bCOOjFJRstauYc6DocQAmZCF61CErAJ5BF2g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-15 17:37 ` Antonio SJ Musumeci
[not found] ` <CAB3-ZyT+xcU-0BnNvq-+GsDe6W8=MCWwxguS-+KQ39gajmM5pw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-15 17:51 ` Nikolaus Rath
2016-01-15 19:29 ` Nikhilesh Reddy
[not found] ` <56994884.9060002-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-01-15 21:38 ` Nikolaus Rath
2016-01-15 21:43 ` Linus Torvalds
2016-01-15 21:46 ` Andy Lutomirski
[not found] ` <CALCETrUA2veiBYYbN1hCSkHxBFyDpe3b=PXg=j53_ZuQBt1FUw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-15 21:53 ` Linus Torvalds
2016-01-19 2:57 ` Nikhilesh Reddy
[not found] ` <569DA62B.7070701-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-01-20 23:24 ` Nikhilesh Reddy
2016-01-15 21:56 ` [fuse-devel] " Hans Beckerus
[not found] ` <5696E366.2080605-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-01-14 8:25 ` Christoph Hellwig
2016-01-14 15:52 ` Nikolaus Rath [this message]
[not found] ` <87mvs8qhun.fsf-Zv899e0YUSYPWKMTL/zdXNi2O/JbrIOy@public.gmane.org>
2016-01-15 9:29 ` Christoph Hellwig
2016-01-19 3:07 ` Jann Horn
[not found] ` <CAK9i0=ojVmbuDiFXY_sHA12vTWgz9aKwEQuZmmYtUka3zqr=hg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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=87mvs8qhun.fsf@thinkpad.rath.org \
--to=nikolaus@rath.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.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=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).