From: Matthew Wilcox <willy@infradead.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: ceph-devel@vger.kernel.org, linux-cachefs@redhat.com,
pfmeec@rit.edu, dhowells@redhat.com, idryomov@gmail.com,
stable@vger.kernel.org, Andrew W Elble <aweits@rit.edu>
Subject: Re: [PATCH v3] ceph: fix write_begin optimization when write is beyond EOF
Date: Sun, 13 Jun 2021 12:04:38 +0100 [thread overview]
Message-ID: <YMXmRo17oy8fDn2b@casper.infradead.org> (raw)
In-Reply-To: <20210612183531.17074-1-jlayton@kernel.org>
On Sat, Jun 12, 2021 at 02:35:31PM -0400, Jeff Layton wrote:
>
> +/**
> + * prep_noread_page - prep a page for writing without reading first
> + * @page: page being prepared
> + * @pos: starting position for the write
> + * @len: length of write
> + *
> + * In some cases we don't need to read at all:
> + * - full page write
> + * - file is currently zero-length
> + * - write that lies in a page that is completely beyond EOF
> + * - write that covers the the page from start to EOF or beyond it
> + *
> + * If any of these criteria are met, then zero out the unwritten parts
> + * of the page and return true. Otherwise, return false.
> + */
> +static bool prep_noread_page(struct page *page, loff_t pos, unsigned int len)
> +{
> + struct inode *inode = page->mapping->host;
> + loff_t i_size = i_size_read(inode);
> + pgoff_t index = pos / PAGE_SIZE;
> + int pos_in_page = pos & ~PAGE_MASK;
Like the helper. A couple of minor tweaks ...
size_t offset = offset_in_page(pos);
> + /* full page write */
> + if (pos_in_page == 0 && len == PAGE_SIZE)
> + goto zero_out;
At some point, we're going to need to pass the full len to
->write_begin, so that we can decide whether it's worth allocating
more than a single page. Could you make 'len' here size_t, and
check for len >= PAGE_SIZE?
(with the current code, the offset of 0 is a redundant check, but
I'd rather see this future-proofed).
next prev parent reply other threads:[~2021-06-13 11:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 19:59 [PATCH] ceph: fix write_begin optimization when write is beyond EOF Jeff Layton
2021-06-11 20:48 ` Matthew Wilcox
2021-06-11 22:20 ` Jeff Layton
2021-06-12 0:11 ` [PATCH v2] " Jeff Layton
2021-06-12 13:36 ` Matthew Wilcox
2021-06-12 18:35 ` [PATCH v3] " Jeff Layton
2021-06-13 11:04 ` Matthew Wilcox [this message]
2021-06-13 11:36 ` [PATCH v4] " Jeff Layton
2021-06-13 12:02 ` Jeff Layton
2021-06-13 15:15 ` Matthew Wilcox
2021-06-13 15:25 ` Jeff Layton
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=YMXmRo17oy8fDn2b@casper.infradead.org \
--to=willy@infradead.org \
--cc=aweits@rit.edu \
--cc=ceph-devel@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-cachefs@redhat.com \
--cc=pfmeec@rit.edu \
--cc=stable@vger.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