From: Liu Bo <bo.li.liu@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v3 1/2] Btrfs: skip merge part for delayed data refs
Date: Thu, 2 May 2013 00:27:37 +0800 [thread overview]
Message-ID: <1367425659-10803-2-git-send-email-bo.li.liu@oracle.com> (raw)
In-Reply-To: <1367425659-10803-1-git-send-email-bo.li.liu@oracle.com>
When we have data deduplication on, we'll hang on the merge part
because it needs to verify every queued delayed data refs related to
this disk offset.
And in the case of delayed data refs, we don't usually have too much
data refs to merge.
So it's safe to shut it down for data refs.
Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
---
fs/btrfs/delayed-ref.c | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/fs/btrfs/delayed-ref.c b/fs/btrfs/delayed-ref.c
index b7a0641..34670c8 100644
--- a/fs/btrfs/delayed-ref.c
+++ b/fs/btrfs/delayed-ref.c
@@ -316,6 +316,13 @@ void btrfs_merge_delayed_refs(struct btrfs_trans_handle *trans,
struct rb_node *node;
u64 seq = 0;
+ /*
+ * We don't have too much refs to merge in the case of delayed data
+ * refs.
+ */
+ if (head->is_data)
+ return;
+
spin_lock(&fs_info->tree_mod_seq_lock);
if (!list_empty(&fs_info->tree_mod_seq_list)) {
struct seq_list *elem;
--
1.7.7
next prev parent reply other threads:[~2013-05-01 16:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 16:27 [RFC PATCH v3 0/2] Online data deduplication Liu Bo
2013-05-01 16:27 ` Liu Bo [this message]
2013-05-01 16:27 ` [PATCH v3 2/2] Btrfs: online " Liu Bo
2013-05-01 17:30 ` Josef Bacik
2013-05-01 18:07 ` Gabriel de Perthuis
2013-05-01 16:27 ` [PATCH] Btrfs-progs: add dedup register Liu Bo
2013-05-13 15:55 ` David Sterba
2013-05-14 0:29 ` Liu Bo
2013-05-01 17:37 ` [RFC PATCH v3 0/2] Online data deduplication Josef Bacik
2013-05-03 7:54 ` 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=1367425659-10803-2-git-send-email-bo.li.liu@oracle.com \
--to=bo.li.liu@oracle.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 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).