From: Nikolay Borisov <nborisov@suse.com>
To: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 16/18] btrfs: introduce btrfs_subpage for data inodes
Date: Mon, 14 Dec 2020 14:46:15 +0200 [thread overview]
Message-ID: <d46012a6-00b8-ebbd-10aa-56773c7e0bbf@suse.com> (raw)
In-Reply-To: <20201210063905.75727-17-wqu@suse.com>
On 10.12.20 г. 8:39 ч., Qu Wenruo wrote:
> To support subpage sector size, data also need extra info to make sure
> which sectors in a page are uptodate/dirty/...
>
> This patch will make pages for data inodes to get btrfs_subpage
> structure attached, and detached when the page is freed.
>
> This patch also slightly changes the timing when
> set_page_extent_mapped() to make sure:
> - We have page->mapping set
> page->mapping->host is used to grab btrfs_fs_info, thus we can only
> call this function after page is mapped to an inode.
>
> One call site attaches pages to inode manually, thus we have to modify
> the timing of set_page_extent_mapped() a little.
>
> - As soon as possible, before other operations
> Since memory allocation can fail, we have to do extra error handling.
> Calling set_page_extent_mapped() as soon as possible can simply the
> error handling for several call sites.
>
> The idea is pretty much the same as iomap_page, but with more bitmaps
> for btrfs specific cases.
>
> Currently the plan is to switch iomap if iomap can provide sector
> aligned write back (only write back dirty sectors, but not the full
> page, data balance require this feature).
>
> So we will stick to btrfs specific bitmap for now.
>
> Signed-off-by: Qu Wenruo <wqu@suse.com>
> ---
> fs/btrfs/compression.c | 10 ++++++--
> fs/btrfs/extent_io.c | 47 +++++++++++++++++++++++++++++++++----
> fs/btrfs/extent_io.h | 3 ++-
> fs/btrfs/file.c | 10 +++++---
> fs/btrfs/free-space-cache.c | 15 +++++++++---
> fs/btrfs/inode.c | 12 ++++++----
> fs/btrfs/ioctl.c | 5 +++-
> fs/btrfs/reflink.c | 5 +++-
> fs/btrfs/relocation.c | 12 ++++++++--
> 9 files changed, 98 insertions(+), 21 deletions(-)
>
> diff --git a/fs/btrfs/compression.c b/fs/btrfs/compression.c
> index 5ae3fa0386b7..6d203acfdeb3 100644
> --- a/fs/btrfs/compression.c
> +++ b/fs/btrfs/compression.c
> @@ -542,13 +542,19 @@ static noinline int add_ra_bio_pages(struct inode *inode,
> goto next;
> }
>
> - end = last_offset + PAGE_SIZE - 1;
> /*
> * at this point, we have a locked page in the page cache
> * for these bytes in the file. But, we have to make
> * sure they map to this compressed extent on disk.
> */
> - set_page_extent_mapped(page);
> + ret = set_page_extent_mapped(page);
> + if (ret < 0) {
> + unlock_page(page);
> + put_page(page);
> + break;
> + }
> +
> + end = last_offset + PAGE_SIZE - 1;
> lock_extent(tree, last_offset, end);
> read_lock(&em_tree->lock);
> em = lookup_extent_mapping(em_tree, last_offset,
> diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
> index 64a19c1884fc..4e4ed9c453ae 100644
> --- a/fs/btrfs/extent_io.c
> +++ b/fs/btrfs/extent_io.c
> @@ -3191,10 +3191,40 @@ static int attach_extent_buffer_page(struct extent_buffer *eb,
> return 0;
> }
>
> -void set_page_extent_mapped(struct page *page)
> +int __must_check set_page_extent_mapped(struct page *page)
> {
> - if (!PagePrivate(page))
> + struct btrfs_fs_info *fs_info;
> +
> + ASSERT(page->mapping);
> +
> + if (PagePrivate(page))
> + return 0;
> +
> + fs_info = btrfs_sb(page->mapping->host->i_sb);
> + if (fs_info->sectorsize == PAGE_SIZE) {
> attach_page_private(page, (void *)EXTENT_PAGE_PRIVATE);
> + return 0;
> + }
> +
> + return btrfs_attach_subpage(fs_info, page);
In all previous patches < PAGE_SIZE is the special case, in this
function it's reversed. For the sake of consistency change that so
btrfs_attch_subpage is executed inside the conditional.
> +}
> +
> +void clear_page_extent_mapped(struct page *page)
> +{
> + struct btrfs_fs_info *fs_info;
> +
> + ASSERT(page->mapping);
> +
> + if (!PagePrivate(page))
> + return;
> +
> + fs_info = btrfs_sb(page->mapping->host->i_sb);
> + if (fs_info->sectorsize == PAGE_SIZE) {
> + detach_page_private(page);
> + return;
> + }
> +
> + btrfs_detach_subpage(fs_info, page);
DITTO
> }
>
> static struct extent_map *
<snip>
> diff --git a/fs/btrfs/file.c b/fs/btrfs/file.c
> index a29b50208eee..9b878616b489 100644
> --- a/fs/btrfs/file.c
> +++ b/fs/btrfs/file.c
> @@ -1373,6 +1373,12 @@ static noinline int prepare_pages(struct inode *inode, struct page **pages,
> goto fail;
> }
>
> + err = set_page_extent_mapped(pages[i]);
> + if (err < 0) {
> + faili = i;
> + goto fail;
> + }
> +
> if (i == 0)
> err = prepare_uptodate_page(inode, pages[i], pos,
> force_uptodate);
> @@ -1470,10 +1476,8 @@ lock_and_cleanup_extent_if_need(struct btrfs_inode *inode, struct page **pages,
> * We'll call btrfs_dirty_pages() later on, and that will flip around
> * delalloc bits and dirty the pages as required.
> */
> - for (i = 0; i < num_pages; i++) {
> - set_page_extent_mapped(pages[i]);
> + for (i = 0; i < num_pages; i++)
> WARN_ON(!PageLocked(pages[i]));
> - }
The comment above this needs to be removed/rewritten I guess?
Essentially that set_page_extent_mapped is moved to prepare_pages.
>
> return ret;
> }
<snip>
> @@ -8355,7 +8357,9 @@ vm_fault_t btrfs_page_mkwrite(struct vm_fault *vmf)
> wait_on_page_writeback(page);
>
> lock_extent_bits(io_tree, page_start, page_end, &cached_state);
> - set_page_extent_mapped(page);
> + ret = set_page_extent_mapped(page);
> + if (ret < 0)
> + goto out_unlock;
You should use ret2, ret in this function is used for the retval of
vmf_error().
>
> /*
> * we can't set the delalloc bits if there are pending ordered
<snip>
next prev parent reply other threads:[~2020-12-14 12:47 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 6:38 [PATCH v2 00/18] btrfs: add read-only support for subpage sector size Qu Wenruo
2020-12-10 6:38 ` [PATCH v2 01/18] btrfs: extent_io: rename @offset parameter to @disk_bytenr for submit_extent_page() Qu Wenruo
2020-12-17 15:44 ` Josef Bacik
2020-12-10 6:38 ` [PATCH v2 02/18] btrfs: extent_io: refactor __extent_writepage_io() to improve readability Qu Wenruo
2020-12-10 12:12 ` Nikolay Borisov
2020-12-10 12:53 ` Qu Wenruo
2020-12-10 12:58 ` Nikolay Borisov
2020-12-17 15:43 ` Josef Bacik
2020-12-10 6:38 ` [PATCH v2 03/18] btrfs: file: update comment for btrfs_dirty_pages() Qu Wenruo
2020-12-10 12:16 ` Nikolay Borisov
2020-12-10 6:38 ` [PATCH v2 04/18] btrfs: extent_io: introduce a helper to grab an existing extent buffer from a page Qu Wenruo
2020-12-10 13:51 ` Nikolay Borisov
2020-12-17 15:50 ` Josef Bacik
2020-12-10 6:38 ` [PATCH v2 05/18] btrfs: extent_io: introduce the skeleton of btrfs_subpage structure Qu Wenruo
2020-12-17 15:52 ` Josef Bacik
2020-12-10 6:38 ` [PATCH v2 06/18] btrfs: extent_io: make attach_extent_buffer_page() to handle subpage case Qu Wenruo
2020-12-10 15:30 ` Nikolay Borisov
2020-12-17 6:48 ` Qu Wenruo
2020-12-10 16:09 ` Nikolay Borisov
2020-12-17 16:00 ` Josef Bacik
2020-12-18 0:44 ` Qu Wenruo
2020-12-18 15:41 ` Josef Bacik
2020-12-19 0:24 ` Qu Wenruo
2020-12-21 10:15 ` Qu Wenruo
2020-12-10 6:38 ` [PATCH v2 07/18] btrfs: extent_io: make grab_extent_buffer_from_page() " Qu Wenruo
2020-12-10 15:39 ` Nikolay Borisov
2020-12-17 6:55 ` Qu Wenruo
2020-12-17 16:02 ` Josef Bacik
2020-12-18 0:49 ` Qu Wenruo
2020-12-10 6:38 ` [PATCH v2 08/18] btrfs: extent_io: support subpage for extent buffer page release Qu Wenruo
2020-12-10 16:13 ` Nikolay Borisov
2020-12-10 6:38 ` [PATCH v2 09/18] btrfs: subpage: introduce helper for subpage uptodate status Qu Wenruo
2020-12-11 10:10 ` Nikolay Borisov
2020-12-11 10:48 ` Qu Wenruo
2020-12-11 11:41 ` Nikolay Borisov
2020-12-11 11:56 ` Qu Wenruo
2020-12-10 6:38 ` [PATCH v2 10/18] btrfs: subpage: introduce helper for subpage error status Qu Wenruo
2020-12-10 6:38 ` [PATCH v2 11/18] btrfs: extent_io: make set/clear_extent_buffer_uptodate() to support subpage size Qu Wenruo
2020-12-10 6:38 ` [PATCH v2 12/18] btrfs: extent_io: implement try_release_extent_buffer() for subpage metadata support Qu Wenruo
2020-12-11 12:00 ` Nikolay Borisov
2020-12-11 12:11 ` Qu Wenruo
2020-12-11 16:57 ` Nikolay Borisov
2020-12-12 1:28 ` Qu Wenruo
2020-12-12 9:26 ` Nikolay Borisov
2020-12-12 10:26 ` Qu Wenruo
2020-12-12 5:44 ` Qu Wenruo
2020-12-12 10:30 ` Nikolay Borisov
2020-12-12 10:31 ` Qu Wenruo
2020-12-10 6:39 ` [PATCH v2 13/18] btrfs: extent_io: introduce read_extent_buffer_subpage() Qu Wenruo
2020-12-10 6:39 ` [PATCH v2 14/18] btrfs: extent_io: make endio_readpage_update_page_status() to handle subpage case Qu Wenruo
2020-12-14 9:57 ` Nikolay Borisov
2020-12-14 10:46 ` Qu Wenruo
2020-12-10 6:39 ` [PATCH v2 15/18] btrfs: disk-io: introduce subpage metadata validation check Qu Wenruo
2020-12-10 13:24 ` kernel test robot
2020-12-10 13:39 ` kernel test robot
2020-12-14 10:21 ` Nikolay Borisov
2020-12-14 10:50 ` Qu Wenruo
2020-12-14 11:17 ` Nikolay Borisov
2020-12-14 11:32 ` Qu Wenruo
2020-12-14 12:40 ` Nikolay Borisov
2020-12-10 6:39 ` [PATCH v2 16/18] btrfs: introduce btrfs_subpage for data inodes Qu Wenruo
2020-12-10 9:44 ` kernel test robot
2020-12-11 0:43 ` kernel test robot
2020-12-14 12:46 ` Nikolay Borisov [this message]
2020-12-10 6:39 ` [PATCH v2 17/18] btrfs: integrate page status update for read path into begin/end_page_read() Qu Wenruo
2020-12-14 13:59 ` Nikolay Borisov
2020-12-10 6:39 ` [PATCH v2 18/18] btrfs: allow RO mount of 4K sector size fs on 64K page system Qu Wenruo
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=d46012a6-00b8-ebbd-10aa-56773c7e0bbf@suse.com \
--to=nborisov@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.com \
/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