From: David Sterba <dsterba@suse.cz>
To: Nikolay Borisov <nborisov@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/6] Refactor nocow path
Date: Mon, 19 Aug 2019 18:42:01 +0200 [thread overview]
Message-ID: <20190819164201.GH24086@twin.jikos.cz> (raw)
In-Reply-To: <20190805144708.5432-1-nborisov@suse.com>
On Mon, Aug 05, 2019 at 05:47:02PM +0300, Nikolay Borisov wrote:
> This series aims at making the nocow path code more understanble. This done by
> doing the following things:
>
> 1. Re-arranging and renaming some variables so that they have more expressive
> names, as well as reducing their scope. Patch 1 does this.
>
> 2. Since run_delalloc_nocow open-codes traversal of the btree it contains a lot
> of checks which do not pertain to the nocow logic per-se, but are there to
> ensure the code has found the correct EXTENT_ITEM. The nocow logic itself
> contains some subtle checks which are non-obvious at first. Patch 2 rectifies
> this by adding appropriate comments.
>
> 3. Patch 3 duplicates the call to btrfs_add_ordered_extent into each branch for
> REGULAR or PREALLOC extents. Despite this duplication I think the code flow
> becomes more streamlined and easier to understand. It also does away with one
> of the local variables.
>
> 4. Patch 4 moves extent checking code into the branch it pertains to.
>
> 5. Patch 5 simplifies the conditions of the main 'if' in that function
>
> 6. Finally, patch 6 removes the BUG_ON that will be triggered in case
> btrfs_add_ordered_extent returned ENOMEM. Now it's replaced with proper graceful
> error handling.
>
> This patchset has been tested with a full xfstest run with -onodatacow option
> mount options set.
>
> Nikolay Borisov (6):
> btrfs: Refactor run_delalloc_nocow
> btrfs: Improve comments around nocow path
> btrfs: Simplify run_delalloc_nocow
> btrfs: Streamline code in run_delalloc_nocow in case of inline extents
> btrfs: Simplify extent type check
> btrfs: Remove BUG_ON from run_delalloc_nocow
The patchset has been in for-next, no problems so far so I'd like to
promote it to misc-next. Patch 2 has some nontrivial changes suggested,
please update and resend. Thanks.
next prev parent reply other threads:[~2019-08-19 16:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 14:47 [PATCH 0/6] Refactor nocow path Nikolay Borisov
2019-08-05 14:47 ` [PATCH 1/6] btrfs: Refactor run_delalloc_nocow Nikolay Borisov
2019-08-21 7:42 ` [PATCH v2 1/2] " Nikolay Borisov
2019-08-21 15:03 ` David Sterba
2019-08-05 14:47 ` [PATCH 2/6] btrfs: Improve comments around nocow path Nikolay Borisov
2019-08-06 10:09 ` Filipe Manana
2019-08-07 8:16 ` Nikolay Borisov
2019-08-07 8:26 ` Filipe Manana
2019-08-21 7:42 ` [PATCH v2 2/2] " Nikolay Borisov
2019-08-21 15:10 ` David Sterba
2019-08-05 14:47 ` [PATCH 3/6] btrfs: Simplify run_delalloc_nocow Nikolay Borisov
2019-08-06 9:01 ` Johannes Thumshirn
2019-08-05 14:47 ` [PATCH 4/6] btrfs: Streamline code in run_delalloc_nocow in case of inline extents Nikolay Borisov
2019-08-21 15:17 ` David Sterba
2019-08-05 14:47 ` [PATCH 5/6] btrfs: Simplify extent type check Nikolay Borisov
2019-08-06 10:14 ` Filipe Manana
2019-08-21 15:40 ` David Sterba
2019-08-21 23:47 ` Qu Wenruo
2019-08-22 5:58 ` Nikolay Borisov
2019-08-22 14:25 ` [PATCH] btrfs: Streamline code in run_delalloc_nocow Nikolay Borisov
2019-08-23 17:27 ` David Sterba
2019-08-05 14:47 ` [PATCH 6/6] btrfs: Remove BUG_ON from run_delalloc_nocow Nikolay Borisov
2019-08-06 10:34 ` Filipe Manana
2019-08-07 8:18 ` Nikolay Borisov
2019-08-21 15:55 ` David Sterba
2019-08-22 14:24 ` [PATCH v2] " Nikolay Borisov
2019-08-23 17:28 ` David Sterba
2019-08-19 16:42 ` David Sterba [this message]
2019-08-21 15:59 ` [PATCH 0/6] Refactor nocow path 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=20190819164201.GH24086@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 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).