From: Matthew Wilcox <willy@infradead.org>
To: David Howells <dhowells@redhat.com>
Cc: trond.myklebust@primarydata.com, darrick.wong@oracle.com,
hch@lst.de, viro@zeniv.linux.org.uk, jlayton@kernel.org,
sfrench@samba.org, torvalds@linux-foundation.org,
linux-nfs@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2 3/5] mm: Make swap_readpage() for SWP_FS_OPS use ->direct_IO() not ->readpage()
Date: Thu, 12 Aug 2021 22:23:46 +0100 [thread overview]
Message-ID: <YRWRYnmoS+zVYqHV@casper.infradead.org> (raw)
In-Reply-To: <162879974434.3306668.4798886633463058599.stgit@warthog.procyon.org.uk>
On Thu, Aug 12, 2021 at 09:22:24PM +0100, David Howells wrote:
> +++ b/include/linux/fs.h
> @@ -336,6 +336,7 @@ struct kiocb {
> union {
> unsigned int ki_cookie; /* for ->iopoll */
> struct wait_page_queue *ki_waitq; /* for async buffered IO */
> + struct page *ki_swap_page; /* For swapfile_read/write */
Nice idea.
> +static void __swapfile_read_complete(struct kiocb *iocb, long ret, long ret2)
I would make this take a struct page * and just one 'ret'.
> +{
> + struct page *page = iocb->ki_swap_page;
> +
> + if (ret == PAGE_SIZE) {
page_size(page)?
> + kiocb.ki_pos = page_file_offset(page);
We talked about swap_file_pos(), right?
> + ret = swap_file->f_mapping->a_ops->direct_IO(&kiocb, &to);
> +
> + __swapfile_read_complete(&kiocb, ret, 0);
> + return (ret > 0) ? 0 : ret;
What if it returns a short read?
> +static int swapfile_read(struct swap_info_struct *sis, struct page *page,
> + bool synchronous)
> +{
> + struct swapfile_kiocb *ki;
> + struct file *swap_file = sis->swap_file;
> + struct bio_vec bv = {
> + .bv_page = page,
> + .bv_len = thp_size(page),
> + .bv_offset = 0
> + };
> + struct iov_iter to;
> + int ret;
> +
> + if (synchronous)
> + return swapfile_read_sync(sis, page);
Seems a shame to set up the bio_vec and iov_iter twice. Maybe call:
iov_iter_bvec(&to, READ, &bv, 1, thp_size(page));
before swapfile_read_sync() and pass a pointer to 'to' to
swapfile_read_sync?
next prev parent reply other threads:[~2021-08-12 21:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 20:21 [RFC PATCH v2 0/5] mm: Fix NFS swapfiles and use DIO for swapfiles David Howells
2021-08-12 20:22 ` [RFC PATCH v2 1/5] nfs: Fix write to swapfile failure due to generic_write_checks() David Howells
2021-08-13 3:09 ` Matthew Wilcox
2021-08-13 7:02 ` Christoph Hellwig
2021-08-19 22:38 ` NeilBrown
2021-08-12 20:22 ` [RFC PATCH v2 2/5] mm: Remove the callback func argument from __swap_writepage() David Howells
2021-08-13 7:03 ` Christoph Hellwig
2021-08-12 20:22 ` [RFC PATCH v2 3/5] mm: Make swap_readpage() for SWP_FS_OPS use ->direct_IO() not ->readpage() David Howells
2021-08-12 21:23 ` Matthew Wilcox [this message]
2021-08-13 7:12 ` Christoph Hellwig
2021-08-12 20:22 ` [RFC PATCH v2 4/5] mm: Make __swap_writepage() do async DIO if asked for it David Howells
2021-08-12 20:22 ` [RFC PATCH v2 5/5] mm: Remove swap BIO paths and only use DIO paths [BROKEN] David Howells
2021-08-13 7:14 ` Christoph Hellwig
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=YRWRYnmoS+zVYqHV@casper.infradead.org \
--to=willy@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=dhowells@redhat.com \
--cc=hch@lst.de \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=sfrench@samba.org \
--cc=torvalds@linux-foundation.org \
--cc=trond.myklebust@primarydata.com \
--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).