From: Nikolay Borisov <nborisov@suse.com>
To: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/8] Cleanup io_tree arguments in extent read/write path
Date: Thu, 6 Feb 2020 15:24:38 +0200 [thread overview]
Message-ID: <3113cf2a-cac2-4a83-bcb2-03b8b143cca4@suse.com> (raw)
In-Reply-To: <cover.1580925977.git.dsterba@suse.com>
On 5.02.20 г. 20:09 ч., David Sterba wrote:
> The io_tree is passed to several functions that do extent page
> read/write, but there's a lot of redundancy and things can be
> simplified.
>
> David Sterba (8):
> btrfs: remove extent_page_data::tree
> btrfs: drop argument tree from submit_extent_page
> btrfs: add assertions for tree == inode->io_tree to extent IO helpers
> btrfs: drop argument tree from btrfs_lock_and_flush_ordered_range
> btrfs: sink argument tree to extent_read_full_page
> btrfs: sink argument tree to __extent_read_full_page
> btrfs: sink arugment tree to contiguous_readpages
> btrfs: sink argument tree to __do_readpage
>
> fs/btrfs/disk-io.c | 4 +---
> fs/btrfs/extent_io.c | 50 ++++++++++++++++-------------------------
> fs/btrfs/extent_io.h | 4 ++--
> fs/btrfs/file.c | 2 +-
> fs/btrfs/inode.c | 6 ++---
> fs/btrfs/ordered-data.c | 8 +++----
> fs/btrfs/ordered-data.h | 3 +--
> 7 files changed, 29 insertions(+), 48 deletions(-)
>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
prev parent reply other threads:[~2020-02-06 13:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 18:09 [PATCH 0/8] Cleanup io_tree arguments in extent read/write path David Sterba
2020-02-05 18:09 ` [PATCH 1/8] btrfs: remove extent_page_data::tree David Sterba
2020-02-06 8:34 ` Anand Jain
2020-02-06 13:32 ` Johannes Thumshirn
2020-02-05 18:09 ` [PATCH 2/8] btrfs: drop argument tree from submit_extent_page David Sterba
2020-02-06 5:58 ` Anand Jain
2020-02-06 13:47 ` David Sterba
2020-02-11 5:00 ` Anand Jain
2020-02-06 13:33 ` Johannes Thumshirn
2020-02-05 18:09 ` [PATCH 3/8] btrfs: add assertions for tree == inode->io_tree to extent IO helpers David Sterba
2020-02-06 13:34 ` Johannes Thumshirn
2020-02-05 18:09 ` [PATCH 4/8] btrfs: drop argument tree from btrfs_lock_and_flush_ordered_range David Sterba
2020-02-06 13:38 ` Johannes Thumshirn
2020-02-05 18:09 ` [PATCH 5/8] btrfs: sink argument tree to extent_read_full_page David Sterba
2020-02-06 13:40 ` Johannes Thumshirn
2020-02-05 18:09 ` [PATCH 6/8] btrfs: sink argument tree to __extent_read_full_page David Sterba
2020-02-06 13:40 ` Johannes Thumshirn
2020-02-05 18:09 ` [PATCH 7/8] btrfs: sink arugment tree to contiguous_readpages David Sterba
2020-02-06 13:42 ` Johannes Thumshirn
2020-02-05 18:09 ` [PATCH 8/8] btrfs: sink argument tree to __do_readpage David Sterba
2020-02-06 13:43 ` Johannes Thumshirn
2020-02-06 13:24 ` Nikolay Borisov [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=3113cf2a-cac2-4a83-bcb2-03b8b143cca4@suse.com \
--to=nborisov@suse.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@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