From: Yan Zheng <zheng.yan@oracle.com>
To: Chris Mason <chris.mason@oracle.com>, linux-btrfs@vger.kernel.org
Subject: [PATCH 0/6] Mixed back reference #2
Date: Tue, 26 May 2009 20:53:55 +0800 [thread overview]
Message-ID: <4A1BE663.3040106@oracle.com> (raw)
Hi,
Here's the 2nd version of mixed back reference patches.
Changes since previous version:
- Add backward compatibility.
- Pack back ref items in extent item.
- Don't increase data extents' reference counts when tree log
references them.
- Remove the BTRFS_BLOCK_NO_OWNER_REF tree block flag, since
it's too difficult to keep the flag consistent. (The purperse
of this flag was helping btrfsck checking the correctness of
the back reference system)
Thanks
Yan, Zheng
reply other threads:[~2009-05-26 12:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A1BE663.3040106@oracle.com \
--to=zheng.yan@oracle.com \
--cc=chris.mason@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