From: Christoph Hellwig <hch@lst.de>
To: Christoph Hellwig <hch@lst.de>, xfs@oss.sgi.com
Subject: Re: [PATCH 0/9] CRC support for superblock, ag headers, log and btree blocks
Date: Fri, 26 Sep 2008 13:10:45 +0200 [thread overview]
Message-ID: <20080926111045.GA4411@lst.de> (raw)
In-Reply-To: <20080925235030.GE27997@disturbed>
On Fri, Sep 26, 2008 at 09:50:30AM +1000, Dave Chinner wrote:
> On Fri, Sep 26, 2008 at 12:56:13AM +0200, Christoph Hellwig wrote:
> > Here's an updated crc series for various metadata structures. We're still
> > looking at the magic number in the log recovery case because getting down
> > a buffer type for the other structures wasn't quite as easy as for the
> > btree block. I'll probably look into that again once we're done with all
> > data structures.
>
> FWIW, I note that you haven't done anything with the AGFL yet. I was
> considering 2 different approaches. The first was to put the CRC for
> the AGFL into the AGF so that the internals of the AGFL do not change.
> However, that means we have interesting synchronisation problems
> with the CRC, so I don't think that will fly.
>
> The other option was to reduce the number of slots in the AGFL by
> one and use the last slot to hold the CRC. I think that is OK to do;
> the AGFL can change size with different secotr size support, so I
> don't see this being a big problem. Nor do I think that we ever fill
> the AGFL up to it's full 128 slots during any transaction, so
> reducing the size by one should be safe.
Yes, my plan was to remove one slot, but use the first one for the crc.
Last one might actually be smarter.
next prev parent reply other threads:[~2008-09-26 11:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 22:56 [PATCH 0/9] CRC support for superblock, ag headers, log and btree blocks Christoph Hellwig
2008-09-25 23:50 ` Dave Chinner
2008-09-26 11:10 ` Christoph Hellwig [this message]
2008-12-01 23:10 ` Bill O'Donnell
[not found] ` <20081203104409.GA15485@infradead.org>
2008-12-04 0:19 ` Bill O'Donnell
2008-12-01 23:22 ` Bill O'Donnell
2008-12-01 23:39 ` Bill O'Donnell
2008-12-01 23:53 ` Bill O'Donnell
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=20080926111045.GA4411@lst.de \
--to=hch@lst.de \
--cc=xfs@oss.sgi.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