From: Chris Mason <chris.mason@oracle.com>
To: Yan Zheng <yanzheng@21cn.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [RFC][PATCH] Fix nodatacow check
Date: Fri, 18 Jul 2008 15:15:44 -0400 [thread overview]
Message-ID: <1216408544.6932.67.camel@think.oraclecorp.com> (raw)
In-Reply-To: <3d0408630807171913r29a1f24he69d80497cd374d7@mail.gmail.com>
On Fri, 2008-07-18 at 10:13 +0800, Yan Zheng wrote:
> Hello,
>
> This patch fixes the nodatacow check. The new test function can always
> detect extents referenced by multiple snatshots. If a extent was
> allocated in recent two transactions and no snapshot happened in these
> two transactions, we can always avoid cow.
Thanks Yan, I think this should work. Could you please update it to the
latest unstable tree and resend?
-chris
prev parent reply other threads:[~2008-07-18 19:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 2:13 [RFC][PATCH] Fix nodatacow check Yan Zheng
2008-07-18 19:15 ` Chris Mason [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=1216408544.6932.67.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=yanzheng@21cn.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