public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: Les Oxley <les@ampex.com>
Cc: xfs@oss.sgi.com
Subject: Re: EXTENT BOUNDARIES
Date: Fri, 19 Jan 2007 19:44:43 -0800	[thread overview]
Message-ID: <20070120034443.GA27654@tuatara.stupidest.org> (raw)
In-Reply-To: <45B137CA.3020206@ampex.com>

On Fri, Jan 19, 2007 at 01:27:38PM -0800, Les Oxley wrote:

> We are looking into running XFS on a 3TB FLASH MEMORY MODULE.

neat, you need to send me some of those

does it wear level and do other clever stuff?  most conventional flash
storage devices don't last long with journalling filesystems...

> We have a question regarding the extent boundaries.  See the
> attached PowerPoint drawing, xfs.ppt We are running Linux.

you're asking linux people to read a powerpoint file?  :-)

you might have better luck with something else

> Our media is 3 million contiguous 4KB blocks.

That's not 3TB, surely it's < 12GB?

> 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.

i didn't open the powerpoint file, so i migth not be answering this
very well...

extent boundaries do not have to be on any boundary

you can tweak mkfs.xfs to affect where AGs start, is that of value to
you?

now, there are also rt volumes which can have larger extents so those
might be of value to you, but you would still need somewhere for the
metadata

  reply	other threads:[~2007-01-20  3:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-19 21:27 EXTENT BOUNDARIES Les Oxley
2007-01-20  3:44 ` Chris Wedgwood [this message]
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=20070120034443.GA27654@tuatara.stupidest.org \
    --to=cw@f00f.org \
    --cc=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