From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com
Subject: RFC: adding a crc field to xfs_buf_log_format_t
Date: Tue, 23 Sep 2008 13:28:00 -0400 [thread overview]
Message-ID: <20080923172800.GA22047@infradead.org> (raw)
With adding CRC to xfs metadata structures we face an interesting
problem. As we want all the CRCs logged we always have to log the CRC.
But this means for many modification that previous just required one
or two chunks of a buffer logged (e.g. superblock counters or changing a
single btree records) we would now need a second iovec. One idea to
avoid this would be to put the crc into a modified version of
xfs_buf_log_format_t. Any opinions wether this is worth the trouble?
next reply other threads:[~2008-09-23 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 17:28 Christoph Hellwig [this message]
2008-09-24 1:05 ` RFC: adding a crc field to xfs_buf_log_format_t Dave Chinner
2008-09-24 7:03 ` Timothy Shimmin
2008-09-24 17:29 ` Christoph Hellwig
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=20080923172800.GA22047@infradead.org \
--to=hch@infradead.org \
--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