From: Josef Bacik <josef@toxicpanda.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Ordered extent flushing refactor
Date: Tue, 7 May 2019 13:39:23 -0400 [thread overview]
Message-ID: <20190507173922.3ollxvt327ii7ats@macbook-pro-91.dhcp.thefacebook.com> (raw)
In-Reply-To: <20190507071924.17643-1-nborisov@suse.com>
On Tue, May 07, 2019 at 10:19:21AM +0300, Nikolay Borisov wrote:
> Here is v2 of factoring out common code when flushing ordered extent. The main
> change in this version is the switch from inode to btrfs_inode for function
> interfaces as per David's feedback.
>
> Nikolay Borisov (3):
> btrfs: Implement btrfs_lock_and_flush_ordered_range
> btrfs: Use newly introduced btrfs_lock_and_flush_ordered_range
> btrfs: Always use a cached extent_state in
> btrfs_lock_and_flush_ordered_range
>
You can add
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
for the whole series. Thanks,
Josef
next prev parent reply other threads:[~2019-05-07 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 7:19 [PATCH v2 0/3] Ordered extent flushing refactor Nikolay Borisov
2019-05-07 7:19 ` [PATCH v2 1/3] btrfs: Implement btrfs_lock_and_flush_ordered_range Nikolay Borisov
2019-05-07 7:19 ` [PATCH v2 2/3] btrfs: Use newly introduced btrfs_lock_and_flush_ordered_range Nikolay Borisov
2019-05-07 7:19 ` [PATCH v2 3/3] btrfs: Always use a cached extent_state in btrfs_lock_and_flush_ordered_range Nikolay Borisov
2019-05-09 15:35 ` David Sterba
2019-05-07 17:39 ` Josef Bacik [this message]
2019-05-10 12:05 ` [PATCH v2 0/3] Ordered extent flushing refactor David Sterba
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=20190507173922.3ollxvt327ii7ats@macbook-pro-91.dhcp.thefacebook.com \
--to=josef@toxicpanda.com \
--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 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).