From: Darrick J. Wong <djwong@kernel.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH v3 1/3] iomap: Permit pages without an iop to enter writeback
Date: Thu, 8 Jul 2021 21:23:45 -0700 [thread overview]
Message-ID: <20210709042345.GS11588@locust> (raw)
In-Reply-To: <20210707115524.2242151-2-agruenba@redhat.com>
On Wed, Jul 07, 2021 at 01:55:22PM +0200, Andreas Gruenbacher wrote:
> Create an iop in the writeback path if one doesn't exist. This allows us
> to avoid creating the iop in some cases. We'll initially do that for pages
> with inline data, but it can be extended to pages which are entirely within
> an extent. It also allows for an iop to be removed from pages in the
> future (eg page split).
>
> Co-developed-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
Seems simple enough...
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> fs/iomap/buffered-io.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/fs/iomap/buffered-io.c b/fs/iomap/buffered-io.c
> index 9023717c5188..598fcfabc337 100644
> --- a/fs/iomap/buffered-io.c
> +++ b/fs/iomap/buffered-io.c
> @@ -1334,14 +1334,13 @@ iomap_writepage_map(struct iomap_writepage_ctx *wpc,
> struct writeback_control *wbc, struct inode *inode,
> struct page *page, u64 end_offset)
> {
> - struct iomap_page *iop = to_iomap_page(page);
> + struct iomap_page *iop = iomap_page_create(inode, page);
> struct iomap_ioend *ioend, *next;
> unsigned len = i_blocksize(inode);
> u64 file_offset; /* file offset of page */
> int error = 0, count = 0, i;
> LIST_HEAD(submit_list);
>
> - WARN_ON_ONCE(i_blocks_per_page(inode, page) > 1 && !iop);
> WARN_ON_ONCE(iop && atomic_read(&iop->write_bytes_pending) != 0);
>
> /*
> --
> 2.26.3
>
next prev parent reply other threads:[~2021-07-09 4:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 11:55 [Cluster-devel] [PATCH v3 0/3] iomap: small block problems Andreas Gruenbacher
2021-07-07 11:55 ` [Cluster-devel] [PATCH v3 1/3] iomap: Permit pages without an iop to enter writeback Andreas Gruenbacher
2021-07-09 4:23 ` Darrick J. Wong [this message]
2021-07-07 11:55 ` [Cluster-devel] [PATCH v3 2/3] iomap: Don't create iomap_page objects for inline files Andreas Gruenbacher
2021-07-07 14:28 ` Matthew Wilcox
2021-07-09 4:27 ` Darrick J. Wong
2021-07-09 6:21 ` Christoph Hellwig
2021-07-09 12:01 ` Matthew Wilcox
2021-07-09 4:28 ` Darrick J. Wong
2021-07-09 6:20 ` Christoph Hellwig
2021-07-07 11:55 ` [Cluster-devel] [PATCH v3 3/3] iomap: Don't create iomap_page objects in iomap_page_mkwrite_actor Andreas Gruenbacher
2021-07-07 14:03 ` Matthew Wilcox
2021-07-09 4:29 ` Darrick J. Wong
2021-07-09 11:07 ` Andreas Gruenbacher
2021-07-09 6:22 ` 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=20210709042345.GS11588@locust \
--to=djwong@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).