From: David Sterba <dsterba@suse.cz>
To: Nikolay Borisov <nborisov@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 0/9] Cleanup metadata page reading path
Date: Tue, 15 Sep 2020 09:43:47 +0200 [thread overview]
Message-ID: <20200915074347.GC1791@twin.jikos.cz> (raw)
In-Reply-To: <20200914093711.13523-1-nborisov@suse.com>
On Mon, Sep 14, 2020 at 12:37:02PM +0300, Nikolay Borisov wrote:
> Here is v2 of the metadata readout cleanups [0]. This series incorporates the
> feedback I received, namely:
>
> * Added justification why removing btree_readpage is safe in Patch 1
> * Dropped Patch 2 (pg_offset remove from btrfs_get_extent) as Qu intends on using
> it in his subpage blocksize work.
> * Add a comment about caller's responsibility for cleanup in Patch 3
> * Added RB for patches which haven't changed since v1 and got RB by Josef.
>
> [0] https://lore.kernel.org/linux-btrfs/20200909094914.29721-1-nborisov@suse.com/T/#t
>
> Nikolay Borisov (9):
> btrfs: Remove btree_readpage
> btrfs: Simplify metadata pages reading
> btrfs: Remove btree_get_extent
> btrfs: Remove btrfs_get_extent indirection from __do_readpage
> btrfs: Remove mirror_num argument from extent_read_full_page
> btrfs: Promote extent_read_full_page to btrfs_readpage
> btrfs: Sink mirror_num argument in extent_read_full_page
> btrfs: Sink read_flags argument into extent_read_full_page
> btrfs: Sink mirror_num argument in __do_readpage
Added to misc-next, thanks.
prev parent reply other threads:[~2020-09-15 7:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 9:37 [PATCH v2 0/9] Cleanup metadata page reading path Nikolay Borisov
2020-09-14 9:37 ` [PATCH v2 1/9] btrfs: Remove btree_readpage Nikolay Borisov
2020-09-14 10:51 ` Qu Wenruo
2020-09-14 9:37 ` [PATCH v2 2/9] btrfs: Simplify metadata pages reading Nikolay Borisov
2020-09-14 11:01 ` Qu Wenruo
2020-09-14 9:37 ` [PATCH v2 3/9] btrfs: Remove btree_get_extent Nikolay Borisov
2020-09-14 9:37 ` [PATCH v2 4/9] btrfs: Remove btrfs_get_extent indirection from __do_readpage Nikolay Borisov
2020-09-14 9:37 ` [PATCH v2 5/9] btrfs: Remove mirror_num argument from extent_read_full_page Nikolay Borisov
2020-09-14 9:37 ` [PATCH v2 6/9] btrfs: Promote extent_read_full_page to btrfs_readpage Nikolay Borisov
2020-09-14 9:37 ` [PATCH v2 7/9] btrfs: Sink mirror_num argument in extent_read_full_page Nikolay Borisov
2020-09-14 10:35 ` Johannes Thumshirn
2020-09-14 10:38 ` Nikolay Borisov
2020-09-14 9:37 ` [PATCH v2 8/9] btrfs: Sink read_flags argument into extent_read_full_page Nikolay Borisov
2020-09-14 9:37 ` [PATCH v2 9/9] btrfs: Sink mirror_num argument in __do_readpage Nikolay Borisov
2020-09-14 10:39 ` [PATCH v2 0/9] Cleanup metadata page reading path Johannes Thumshirn
2020-09-14 11:39 ` Nikolay Borisov
2020-09-14 11:44 ` Johannes Thumshirn
2020-09-14 11:39 ` [PATCH] btrfs: Opencode extent_read_full_page to its sole caller Nikolay Borisov
2020-09-14 11:45 ` Johannes Thumshirn
2020-09-15 7:44 ` David Sterba
2020-09-15 7:43 ` David Sterba [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=20200915074347.GC1791@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.