From: Josh Triplett <josh@joshtriplett.org>
To: Alessio Balsini <balsini@android.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: FUSE passthrough after opening?
Date: Fri, 22 Mar 2024 15:25:16 +0000 [thread overview]
Message-ID: <Zf2i3MJrKRsp-fkZ@localhost> (raw)
I'm really happy to see the FUSE passthrough support merged!
I have a use case for which it'd be nice to start FUSE passthrough
some time after the initial open: I have a network-backed filesystem,
and in some cases I'd like to serve an initial request before retrieving
the full file. For instance, for a library .so file, I'd love to service
the initial 832-byte read while still downloading the full file.
Would it be possible to add support for transitioning an open FUSE file
to being backed by passthrough *after* the initial open? Could that work
with the current passthrough architecture? (I realize that this might be
more complex, as the initial open is a good time to directly substitute
a file from the underlying filesystem.)
Thanks,
Josh Triplett
reply other threads:[~2024-03-22 15:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Zf2i3MJrKRsp-fkZ@localhost \
--to=josh@joshtriplett.org \
--cc=balsini@android.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).