From: David Sterba <dsterba@suse.cz>
To: Goldwyn Rodrigues <rgoldwyn@suse.de>
Cc: linux-btrfs@vger.kernel.org, Dave Sterba <DSterba@suse.cz>
Subject: Re: [PATCH v3] btrfs: remove force argument from run_delalloc_nocow()
Date: Thu, 4 Mar 2021 18:32:36 +0100 [thread overview]
Message-ID: <20210304173236.GT7604@twin.jikos.cz> (raw)
In-Reply-To: <20210304150625.idi3d6gpkwwovcpz@fiona>
On Thu, Mar 04, 2021 at 09:06:25AM -0600, Goldwyn Rodrigues wrote:
> force_nocow can be calculated by btrfs_inode and does not need to be
> passed as an argument.
>
> This simplifies run_delalloc_nocow() call from btrfs_run_delalloc_range()
> A new function, should_nocow() checks if the range should be nocow'd or
> not. The function returns true iff either BTRFS_INODE_NODATA or
> BTRFS_INODE_PREALLOC, but is not a defrag extent.
>
> Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>
> Reviewed-by: David Sterba <dsterba@suse.com>
> Tested-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
> Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Added to misc-next, thanks.
prev parent reply other threads:[~2021-03-04 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 15:06 [PATCH v3] btrfs: remove force argument from run_delalloc_nocow() Goldwyn Rodrigues
2021-03-04 17:32 ` 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=20210304173236.GT7604@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=rgoldwyn@suse.de \
/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