From: Brad Boyer <flar@allandria.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, jens.axboe@oracle.com,
linux-kernel@vger.kernel.org
Subject: Re: [patch 3/3] splice: implement default splice_read method
Date: Mon, 30 Mar 2009 13:59:28 -0700 [thread overview]
Message-ID: <20090330205927.GA7707@cynthia.pants.nu> (raw)
In-Reply-To: <E1LoNie-0007m5-B4@pomaz-ex.szeredi.hu>
On Mon, Mar 30, 2009 at 10:04:28PM +0200, Miklos Szeredi wrote:
> From: Miklos Szeredi <mszeredi@suse.cz>
>
> If f_op->splice_read() is not implemented fall back to a plain read.
> Use vfs_readv() to read into previously allocated pages.
>
> This will allow splice and functions using splice, such as the loop
> device, to work on all filesystems. This includes "direct_io" files
> in fuse which bypass the page cache.
Based on your description, I would have expected this patch to make
the loop driver work seamlessly. Unless I'm misreading something, I
think the loop driver will still error out if the fs driver in question
doesn't explicitly set splice_read.o
>From drivers/block/loop.c:
724 /* new backing store needs to support loop (eg splice_read) */
725 if (!inode->i_fop->splice_read)
726 goto out_putf;
727
Did you accidentally leave out some changes? Please let me know if I
am missing something obvious.
Brad Boyer
flar@allandria.com
next prev parent reply other threads:[~2009-03-30 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 20:00 [patch 0/3] fuse: implement missing functionality on "direct_io" files Miklos Szeredi
2009-03-30 20:02 ` [patch 1/3] fuse: allow kernel to access " Miklos Szeredi
2009-03-30 20:03 ` [patch 2/3] fuse: allow private mappings of " Miklos Szeredi
2009-03-30 20:04 ` [patch 3/3] splice: implement default splice_read method Miklos Szeredi
2009-03-30 20:59 ` Brad Boyer [this message]
2009-03-31 10:07 ` Miklos Szeredi
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=20090330205927.GA7707@cynthia.pants.nu \
--to=flar@allandria.com \
--cc=jens.axboe@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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
all inboxes | Powered by JetHome®