From: Boaz Harrosh <bharrosh@panasas.com>
To: Jim Rees <rees@merit.edu>
Cc: linux-nfs@vger.kernel.org, peter honeyman <honey@citi.umich.edu>
Subject: Re: stripe definitions
Date: Tue, 22 Feb 2011 20:46:06 -0800 [thread overview]
Message-ID: <4D64910E.1030202@panasas.com> (raw)
In-Reply-To: <20110222200558.GC7545@merit.edu>
On 02/22/2011 12:05 PM, Jim Rees wrote:
> 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.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
You are right stripe_unit is the the bytes to write to a single
device before advancing to the next device. The comment is wrong
the "size of stripe in bytes" is stripe_unit * num_of_devices.
The same name used in the OSD and files layout and has the same
meaning.
Cheers
Boaz
prev parent reply other threads:[~2011-02-23 4:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 20:05 stripe definitions Jim Rees
2011-02-23 4:46 ` Boaz Harrosh [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=4D64910E.1030202@panasas.com \
--to=bharrosh@panasas.com \
--cc=honey@citi.umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@merit.edu \
/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.