From: Liu Bo <bo.li.liu@oracle.com>
To: Josef Bacik <jbacik@fb.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/3] Btrfs: don't set and clear delalloc for O_DIRECT writes
Date: Thu, 12 Feb 2015 12:45:39 +0800 [thread overview]
Message-ID: <20150212044539.GC2416@localhost.localdomain> (raw)
In-Reply-To: <1423685339-8278-2-git-send-email-jbacik@fb.com>
On Wed, Feb 11, 2015 at 03:08:58PM -0500, Josef Bacik wrote:
> We do this to get the space accounting, but this is just needless churn on the
> io_tree, so just drop setting/clearing delalloc and just drop the reserved data
> space when we have a successfull allocation. Thanks,
>
Looks good.
Reviewed-by: Liu Bo <bo.li.liu@oracle.com>
> Signed-off-by: Josef Bacik <jbacik@fb.com>
> ---
> fs/btrfs/inode.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
> index e78a2fd..fb16fd3 100644
> --- a/fs/btrfs/inode.c
> +++ b/fs/btrfs/inode.c
> @@ -7142,7 +7142,7 @@ static int btrfs_get_blocks_direct(struct inode *inode, sector_t iblock,
> int ret = 0;
>
> if (create)
> - unlock_bits |= EXTENT_DELALLOC | EXTENT_DIRTY;
> + unlock_bits |= EXTENT_DIRTY;
> else
> len = min_t(u64, len, root->sectorsize);
>
> @@ -7278,11 +7278,7 @@ unlock:
> BTRFS_I(inode)->outstanding_extents++;
> spin_unlock(&BTRFS_I(inode)->lock);
> }
> -
> - ret = set_extent_bit(&BTRFS_I(inode)->io_tree, lockstart,
> - lockstart + len - 1, EXTENT_DELALLOC, NULL,
> - &cached_state, GFP_NOFS);
> - BUG_ON(ret);
> + btrfs_free_reserved_data_space(inode, len);
> }
>
> /*
> --
> 1.8.3.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-02-12 4:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 20:08 [PATCH 1/3] Btrfs: only adjust outstanding_extents when we do a short write Josef Bacik
2015-02-11 20:08 ` [PATCH 2/3] Btrfs: don't set and clear delalloc for O_DIRECT writes Josef Bacik
2015-02-12 4:45 ` Liu Bo [this message]
2015-02-11 20:08 ` [PATCH 3/3] Btrfs: account for large extents with enospc Josef Bacik
2015-02-12 4:36 ` Liu Bo
2015-02-12 14:53 ` Josef Bacik
2015-02-12 16:16 ` [PATCH 3/3 v2] " Josef Bacik
2015-02-13 2:06 ` Liu Bo
2015-02-13 15:44 ` David Sterba
2015-03-06 20:01 ` [PATCH 3/3] " Filipe David Manana
2015-02-12 3:52 ` [PATCH 1/3] Btrfs: only adjust outstanding_extents when we do a short write Liu Bo
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=20150212044539.GC2416@localhost.localdomain \
--to=bo.li.liu@oracle.com \
--cc=jbacik@fb.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 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.