From: Jens Axboe <axboe@kernel.dk>
To: David Hildenbrand <david@redhat.com>,
David Howells <dhowells@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>
Cc: Matthew Wilcox <willy@infradead.org>, Jan Kara <jack@suse.cz>,
Jeff Layton <jlayton@kernel.org>,
Jason Gunthorpe <jgg@nvidia.com>,
Logan Gunthorpe <logang@deltatee.com>,
Hillf Danton <hdanton@sina.com>,
linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v3 0/5] iov_iter: Adjust styling/location of new splice functions
Date: Tue, 14 Feb 2023 08:36:29 -0700 [thread overview]
Message-ID: <9dd98aed-0d9a-eb3e-790c-0dd744be8ccb@kernel.dk> (raw)
In-Reply-To: <75d74adc-7f18-d0df-e092-10bca4f05f2a@redhat.com>
On 2/14/23 2:07?AM, David Hildenbrand wrote:
> On 14.02.23 09:37, David Howells wrote:
>> Hi Jens, Al, Christoph,
>>
>> Here are patches to make some changes that Christoph requested[1] to the
>> new generic file splice functions that I implemented[2]. Apart from one
>> functional change, they just altering the styling and move one of the
>> functions to a different file:
>>
>> (1) Rename the main functions:
>>
>> generic_file_buffered_splice_read() -> filemap_splice_read()
>> generic_file_direct_splice_read() -> direct_splice_read()
>>
>> (2) Abstract out the calculation of the location of the head pipe buffer
>> into a helper function in linux/pipe_fs_i.h.
>>
>> (3) Use init_sync_kiocb() in filemap_splice_read().
>>
>> This is where the functional change is. Some kiocb fields are then
>> filled in where they were set to 0 before, including setting ki_flags
>> from f_iocb_flags.
>>
>> (4) Move filemap_splice_read() to mm/filemap.c. filemap_get_pages() can
>> then be made static again.
>>
>> (5) Fix splice-read for a number of filesystems that don't provide a
>> ->read_folio() op and for which filemap_get_pages() cannot be used.
>>
>> I've pushed the patches here also:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=iov-extract-3
>>
>> I've also updated worked the changes into the commits on my iov-extract
>> branch if that would be preferable, though that means Jens would need to
>> update his for-6.3/iov-extract again.
>>
>> David
>>
>> Link: https://lore.kernel.org/r/Y+n0n2UE8BQa/OwW@infradead.org/ [1]
>> Link: https://lore.kernel.org/r/20230207171305.3716974-1-dhowells@redhat.com/ [2]
>>
>> Changes
>> =======
>> ver #3)
>> - Fix filesystems/drivers that don't have ->read_folio().
>>
>> ver #2)
>> - Don't attempt to filter IOCB_* flags in filemap_splice_read().
>>
>> Link: https://lore.kernel.org/r/20230213134619.2198965-1-dhowells@redhat.com/ # v1
>>
>
> You ignored my RB's :(
>
> .. but unrelated, what's the plan with this now? As Jens mentioned, it
> might be better to wait for 6.4 for the full series, in which case
> folding this series into the other series would be better.
That is indeed the question, and unanswered so far... Let's turn it into
one clean series, and get it stuffed into for-next and most likely
target 6.4 for inclusion at this point.
--
Jens Axboe
next prev parent reply other threads:[~2023-02-14 15:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 8:37 [PATCH v3 0/5] iov_iter: Adjust styling/location of new splice functions David Howells
2023-02-14 8:37 ` [PATCH v3 1/5] splice: Rename " David Howells
2023-02-14 8:37 ` [PATCH v3 2/5] splice: Provide pipe_head_buf() helper David Howells
2023-02-14 8:37 ` [PATCH v3 3/5] splice: Use init_sync_kiocb() in filemap_splice_read() David Howells
2023-02-14 8:37 ` [PATCH v3 4/5] splice: Move filemap_read_splice() to mm/filemap.c David Howells
2023-02-14 8:37 ` [PATCH v3 5/5] shmem, overlayfs, coda, tty, proc, kernfs, random: Fix splice-read David Howells
2023-02-14 8:54 ` Greg Kroah-Hartman
2023-02-14 13:59 ` Daniel Golle
2023-02-14 13:05 ` Miklos Szeredi
[not found] ` <75d74adc-7f18-d0df-e092-10bca4f05f2a@redhat.com>
2023-02-14 15:36 ` Jens Axboe [this message]
2023-02-14 15:49 ` [PATCH v3 0/5] iov_iter: Adjust styling/location of new splice functions David Howells
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=9dd98aed-0d9a-eb3e-790c-0dd744be8ccb@kernel.dk \
--to=axboe@kernel.dk \
--cc=david@redhat.com \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=hdanton@sina.com \
--cc=jack@suse.cz \
--cc=jgg@nvidia.com \
--cc=jlayton@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=logang@deltatee.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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).