From: Jens Axboe <axboe@kernel.dk>
To: 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>,
David Hildenbrand <david@redhat.com>,
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 v2 0/4] iov_iter: Adjust styling/location of new splice functions
Date: Mon, 13 Feb 2023 10:04:52 -0700 [thread overview]
Message-ID: <1f716ecb-3f27-af5f-66b4-ac4dae52cf23@kernel.dk> (raw)
In-Reply-To: <20230213153301.2338806-1-dhowells@redhat.com>
On 2/13/23 8:32 AM, 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. I've filtered out IOCB_NOWAIT as the function is
> supposed to be synchronous.
>
> (4) Move filemap_splice_read() to mm/filemap.c. filemap_get_pages() can
> then be made static again.
>
> 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.
Honestly, it's getting tight on timing at this point, and there's also
a crash report from today:
https://lore.kernel.org/linux-block/Y+pdHFFTk1TTEBsO@makrotopia.org/
I think we'd be better off folding in this series and then potentially
pushing this series to 6.4 rather than 6.3.
--
Jens Axboe
prev parent reply other threads:[~2023-02-13 17:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 15:32 [PATCH v2 0/4] iov_iter: Adjust styling/location of new splice functions David Howells
2023-02-13 15:32 ` [PATCH v2 1/4] splice: Rename " David Howells
2023-02-13 15:47 ` David Hildenbrand
2023-02-13 15:32 ` [PATCH v2 2/4] splice: Provide pipe_head_buf() helper David Howells
2023-02-13 15:48 ` David Hildenbrand
2023-02-13 15:33 ` [PATCH v2 3/4] splice: Use init_sync_kiocb() in filemap_splice_read() David Howells
2023-02-13 15:50 ` David Hildenbrand
2023-02-13 15:33 ` [PATCH v2 4/4] splice: Move filemap_read_splice() to mm/filemap.c David Howells
2023-02-13 15:52 ` David Hildenbrand
2023-02-13 17:04 ` Jens Axboe [this message]
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=1f716ecb-3f27-af5f-66b4-ac4dae52cf23@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).