From: Jim Rees <rees@merit.edu>
To: linux-nfs@vger.kernel.org
Cc: peter honeyman <honey@citi.umich.edu>
Subject: stripe definitions
Date: Tue, 22 Feb 2011 15:05:58 -0500 [thread overview]
Message-ID: <20110222200558.GC7545@merit.edu> (raw)
There's an inconsistency in rfc5663 that had me a bit confused:
/// struct pnfs_block_stripe_volume_info4 {
/// length4 bsv_stripe_unit; /* size of stripe in bytes */
The comment "size of stripe in bytes" fits the definition of "stripe width"
from rfc5661 section 13.2, but that's not what's meant here. The field
name, "stripe_unit", is correct.
next reply other threads:[~2011-02-22 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 20:05 Jim Rees [this message]
2011-02-23 4:46 ` stripe definitions Boaz Harrosh
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=20110222200558.GC7545@merit.edu \
--to=rees@merit.edu \
--cc=honey@citi.umich.edu \
--cc=linux-nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.