linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ric Wheeler <rwheeler@redhat.com>
To: Chris Samuel <chris@csamuel.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: TRIM support
Date: Mon, 11 Jul 2011 08:17:56 +0100	[thread overview]
Message-ID: <4E1AA3A4.2050908@redhat.com> (raw)
In-Reply-To: <201107111553.17293.chris@csamuel.org>

On 07/11/2011 06:53 AM, Chris Samuel wrote:
> On Mon, 11 Jul 2011 07:59:54 AM Fajar A. Nugraha wrote:
>
>> Sandforce-based SSDs have their own way of reducing writes
>> (e.g. by using internal compression), so you don't have to
>> do anything special
> Not just compression, but also block level de-duplication too
> (i.e. potentially removing the redundancy of btrfs's duplication
> of metadata for safety).
>
> cheers,
> Chris

How vendors implement their internal firmware at any given point is not 
something that we can know (or should know).

As mentioned in this thread, you can and should always measure the performance 
of your application on your OS with and without discard being enabled. Note that 
you might have long term effects (i.e., trim enabled via discard might avoid the 
performance hit you see with some devices after extensive use, especially when 
full).

Keep in mind that discard support is built on an industry standard command and 
is used by other vendors (including windows) so manufacturers that do a bad job 
and suffer performance impacts will be *very* motivated to fix their firmware :)

Ric


      reply	other threads:[~2011-07-11  7:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-02 18:08 TRIM support Leonidas Spyropoulos
2011-07-02 19:45 ` Calvin Walton
     [not found]   ` <CAAeznTrfX9u9YXAz31cjsR=qxqrsnaPHLjZxqTaO4SDVBicF6A@mail.gmail.com>
2011-07-02 22:40     ` Leonidas Spyropoulos
2011-07-03 12:20       ` Hubert Kario
2011-07-03 12:56         ` Leonidas Spyropoulos
2011-07-03 14:46           ` Hubert Kario
     [not found]           ` <201107031654.03363.kario@wit.edu.pl>
     [not found]             ` <CAAeznTqPdQ99Qv7jFFthsZPdHN7ZedPszEJKhpe18gBEvR8=JQ@mail.gmail.com>
2011-07-03 15:28               ` Fwd: " Leonidas Spyropoulos
2011-07-04 16:20   ` Martin Steigerwald
2011-07-04 16:32     ` Leonidas Spyropoulos
2011-07-04 19:51       ` Martin Steigerwald
2011-07-10  8:33   ` Chris Samuel
2011-07-10 20:58     ` Leonidas Spyropoulos
2011-07-10 21:59       ` Fajar A. Nugraha
2011-07-10 22:34         ` Leonidas Spyropoulos
2011-07-11  6:04           ` Fajar A. Nugraha
2011-07-11  7:02             ` Leonidas Spyropoulos
2011-07-11  7:19               ` Fajar A. Nugraha
2011-07-11  5:53         ` Chris Samuel
2011-07-11  7:17           ` Ric Wheeler [this message]

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=4E1AA3A4.2050908@redhat.com \
    --to=rwheeler@redhat.com \
    --cc=chris@csamuel.org \
    --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).