From: Les Oxley <les@ampex.com>
To: xfs@oss.sgi.com
Subject: EXTENT BOUNDARIES
Date: Fri, 19 Jan 2007 13:27:38 -0800 [thread overview]
Message-ID: <45B137CA.3020206@ampex.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
Hello,
We are looking into running XFS on a 3TB FLASH MEMORY MODULE. We have a
question regarding the extent boundaries.
See the attached PowerPoint drawing, xfs.ppt We are running Linux.
Our media is 3 million contiguous 4KB blocks. We would like to define
an extent size of 1MB and this tracks the erasure block size
of the flash memory, and that greatly improves perfomance. We are trying
to understand where XFS places the extent boundaries with reference to
the contiguous block sequence.
Is this deterministic as indicated in the drawing ? That is, are the
extent boundaries on 256 block boundaries.
Any help would be greatly appreciated.
Les Oxley
Ampex Corporation
Redwood City
California.
[-- Attachment #2: xfs.ppt --]
[-- Type: application/vnd.ms-powerpoint, Size: 23040 bytes --]
next reply other threads:[~2007-01-19 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 21:27 Les Oxley [this message]
2007-01-20 3:44 ` EXTENT BOUNDARIES Chris Wedgwood
2007-01-20 4:34 ` Eric Sandeen
2007-01-23 3:08 ` Barry Naujok
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=45B137CA.3020206@ampex.com \
--to=les@ampex.com \
--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