Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Dongjun Shin <djshin90@gmail.com>
To: Dmitri Nikulin <dnikulin@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: ssd optimised mode
Date: Mon, 23 Feb 2009 12:15:51 +0900	[thread overview]
Message-ID: <7fe698080902221915w6f961227ub26abae7f57302ae@mail.gmail.com> (raw)
In-Reply-To: <3a7f57190902221833i61beb82u38c29dda0eaf5f42@mail.gmail.com>

On Mon, Feb 23, 2009 at 11:33 AM, Dmitri Nikulin <dnikulin@gmail.com> wrote:
> On Mon, Feb 23, 2009 at 12:22 PM, Dongjun Shin <djshin90@gmail.com> wrote:
>> A well-designed SSD should survive power cycling and should provide atomicity
>> of flush operation regardless of the underlying flash operations. I don't expect
>> that users of SSD have different requirements about atomicity.
>
> Well that's my point, it "should" provide atomicity, but is this the
> case for consumer SSDs? It is certainly NOT the case for cheap
> USB-based flash media and AFAIK not for CF either.
>

AFAIK, all enterprise and consumer SSDs have atomicity requirements
because they're designed to replace the HDD without changes to the OS.

USB or any kind of flash-based cards have different requirements.
They're optimized for cost and the priority for the atomicity is low.
Moreover, they can be plugged out without prior notice to OS.

-- 
Dongjun

  reply	other threads:[~2009-02-23  3:15 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 [this message]
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
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=7fe698080902221915w6f961227ub26abae7f57302ae@mail.gmail.com \
    --to=djshin90@gmail.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