linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Subject: data alignment for SSD: Stripe size or sector size given with -s?
Date: Sat, 14 May 2011 09:31:26 +0200	[thread overview]
Message-ID: <201105140931.26389.Martin@lichtvoll.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]

Hi!

> [ANNOUNCE] Btrfs v0.9
> [...]
> * Stripe size parameter to mkfs.btrfs (-s size_in_bytes). Extents will
>  be aligned to the stripe size for performance.
> [...]
http://fixunix.com/kernel/258991-[announce]-btrfs-v0-9-a.html

versus

>        -s, --sectorsize size
>               Specify the sectorsize, the minimum block allocation.

(man mkfs.btrfs with btrfs-tools 0.19+20101101-1 debian package).

Which one applies? Or do both mention the same? My notion of a sector is 
something different tough.

I wonder how to set a stripe size for alignment to erase blocks of an 
Intel SSD 320. Or whether to set anything at all. I want to try to use GPT 
with ThinkPad T520 UEFI BIOS.

I read from Chris that metadata is basically aligned at 2 MiB already with 
mount option "ssd" which is default for non rotational media:

> Today, metadata allocations are 4k aligned but we do metadata
> allocations in cluster of 256k in size (2MB in size in mount -o ssd
> mode).  This results in larger metadata writes, and more contiguous
> metadata writes.  The larger writes give the SSD FTL a better chance of
> doing more optimal management of the flash.

(Re: SSDs and filesystem alignment... from 2009-02-23,
Message-Id: <1235398980.11205.5.camel@think.oraclecorp.com>)

But what about data alignment?

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

                 reply	other threads:[~2011-05-14  7:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201105140931.26389.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).