From: Dave Chinner <david@fromorbit.com>
To: Raz <raziebe@gmail.com>
Cc: linux-xfs@oss.sgi.com, Eric Sandeen <sandeen@sandeen.net>
Subject: Re: XFS over SSD
Date: Mon, 15 Dec 2008 16:36:57 +1100 [thread overview]
Message-ID: <20081215053656.GE32301@disturbed> (raw)
In-Reply-To: <5d96567b0812080711x34bb93d6vd8e4f88d9b190e9@mail.gmail.com>
On Mon, Dec 08, 2008 at 05:11:58PM +0200, Raz wrote:
> On Mon, Dec 8, 2008 at 4:46 PM, Eric Sandeen <sandeen@sandeen.net> wrote:
> > Raz wrote:
> >> I am thinking of using XFS over a SSD disk.
> >> 1. Can I separate xfs meta data ( not just the logging) from the SSD ?
> >> can I put the meta on a different disk ?
> >
> > Are you talking about just the log (see the mkfs man page for external
> > logs, as Justin suggested) or all metadata? For the latter, using the
> > realtime subvolume does accomplish this (data on one volume, metadata on
> > the other) but that's not used very often.
> >
> > -Eric
> >
> I am referring to all the meta data. 128K of erase block for some block map
> update is a big penalty.
That's not an issue for smart SSDs like the intel one. They
internally use a log-based structure that means that small writes
don't end up requiring an entire erase block to be rewritten. That
is, they have a low write amplification factor.
Such SSDs don't really care that much about the filesystem structure
and random write patterns. Older/cheaper SSDs have a much larger
write amplification factor and so are unsuited to traditional
filesystem structures.....
Google "SSD write amplification" for more information.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2008-12-15 5:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 12:42 XFS over SSD Raz
2008-12-08 13:31 ` Justin Piszcz
2008-12-08 14:46 ` Eric Sandeen
2008-12-08 15:11 ` Raz
2008-12-08 15:50 ` Eric Sandeen
2008-12-15 5:36 ` Dave Chinner [this message]
2008-12-09 7:53 ` Emmanuel Florac
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=20081215053656.GE32301@disturbed \
--to=david@fromorbit.com \
--cc=linux-xfs@oss.sgi.com \
--cc=raziebe@gmail.com \
--cc=sandeen@sandeen.net \
/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.