From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: What about storing more crc32 in the unused csum size for metadata?
Date: Mon, 12 Jan 2015 05:23:16 +0000 (UTC) [thread overview]
Message-ID: <pan$279da$6f12814e$e8e5572b$d2a90667@cox.net> (raw)
In-Reply-To: 54B353EE.6090605@cn.fujitsu.com
Qu Wenruo posted on Mon, 12 Jan 2015 12:56:14 +0800 as excerpted:
> Oh, my fault, sector 1 should contains csum for the second eighth of the
> leaf/node...
> Since the first eighth csum can be calculated vice verse.
>
> Thanks,
Thanks indeed.
/Now/ it makes sense. Skip the one and reverse-calculate it. (Which you
had actually implied and I guess it doesn't matter which one as long as
it's /only/ one, but given my general unfamiliarity with crc at a
practical level and impaired logic state, and your hiding it in the ...
gap, I needed a bit more help to make the leap. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2015-01-12 5:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 2:32 What about storing more crc32 in the unused csum size for metadata? Qu Wenruo
2015-01-12 4:52 ` Duncan
2015-01-12 4:56 ` Qu Wenruo
2015-01-12 5:23 ` Duncan [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='pan$279da$6f12814e$e8e5572b$d2a90667@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).