From: Chris Mason <chris.mason@oracle.com>
To: Dmitri Nikulin <dnikulin@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: ssd optimised mode
Date: Mon, 23 Feb 2009 09:33:13 -0500 [thread overview]
Message-ID: <1235399593.11205.15.camel@think.oraclecorp.com> (raw)
In-Reply-To: <3a7f57190902211707h37ff1478vdc0e5ffff66fa4da@mail.gmail.com>
On Sun, 2009-02-22 at 12:07 +1100, Dmitri Nikulin wrote:
> On Sat, Feb 21, 2009 at 3:30 AM, Chris Mason <chris.mason@oracle.com> wrote:
> > The short answer is that in ssd mode we don't try to avoid random reads.
>
> In the ideal future where SSDs can be run without a flimsy hardware
> FTL, and btrfs can use something like ubi directly, would SSD mode
> also be able to enable more intelligent wear levelling and safer use
> of eraseblocks?
I think this kind of future is less and less likely. SSD makers are
going to differentiate themselves via their FTL, and they are not going
to give the OS the chance to mess around with the flash directly.
There will surely be exceptions, but I don't think we're going to find
them in a dell any time soon.
>
> I've read that one of the potentially crippling limitations of ZFS is
> that even its reliability features depend largely on being able to
> perform atomic writes, which are currently impossible (?) on flash
> media where a block has to be erased before it can be updated, clearly
> not an atomic operation. Is there any solution to this that doesn't
> depend on a battery backup? Clearly it's not something a filesystem
> can practically solve.
I'm sure that some early flash drives got this wrong, but the crummy
drives will eventually drop out of the market as the reliable ones gain
traction.
-chris
next prev parent reply other threads:[~2009-02-23 14:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 11:26 ssd optimised mode srimugunthan dhandapani
2009-02-20 16:01 ` Josef Bacik
2009-02-20 16:30 ` Chris Mason
2009-02-22 1:07 ` Dmitri Nikulin
2009-02-22 17:44 ` Steven Pratt
2009-02-23 1:06 ` Dmitri Nikulin
2009-02-23 1:22 ` Dongjun Shin
2009-02-23 2:33 ` Dmitri Nikulin
2009-02-23 3:15 ` Dongjun Shin
2009-02-23 3:17 ` Seth Huang
2009-02-23 4:01 ` Dmitri Nikulin
2009-02-23 9:31 ` Oliver Mattos
2009-02-23 16:40 ` Martin K. Petersen
2009-02-23 16:48 ` Claudio Martins
2009-02-23 17:23 ` Martin K. Petersen
2009-02-23 14:33 ` Chris Mason [this message]
2009-02-24 0:16 ` Dmitri Nikulin
2009-02-24 0:35 ` Dongjun Shin
2009-02-24 2:32 ` Martin K. Petersen
2009-02-24 3:53 ` Dmitri Nikulin
2009-02-24 4:09 ` Dongjun Shin
2009-02-24 4:10 ` Martin K. Petersen
2009-02-24 4:23 ` Dmitri Nikulin
2009-02-23 22:19 ` Wes Felter
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=1235399593.11205.15.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=dnikulin@gmail.com \
--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