linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leonidas Spyropoulos <artafinde@gmail.com>
To: "Fajar A. Nugraha" <list@fajar.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: TRIM support
Date: Sun, 10 Jul 2011 23:34:08 +0100	[thread overview]
Message-ID: <CAAeznTp-XB2eGarkfyVRASyLTULYLz0myPE+GN6TggrxPjv_YA@mail.gmail.com> (raw)
In-Reply-To: <CAG1y0seg-TTgbdr5_xTjaA_rYoW44AF_pPAFC5_nCNG1qEmNHg@mail.gmail.com>

So any clues for the intel 320 series? I think it doesn't use compressi=
on.

On Sun, Jul 10, 2011 at 10:59 PM, Fajar A. Nugraha <list@fajar.net> wro=
te:
> On Mon, Jul 11, 2011 at 3:58 AM, Leonidas Spyropoulos
> <artafinde@gmail.com> wrote:
>> On Sun, Jul 10, 2011 at 9:33 AM, Chris Samuel <chris@csamuel.org> wr=
ote:
>>> On Sun, 3 Jul 2011 05:45:17 AM Calvin Walton wrote:
>>> This LWN article from 2009 explains why it can be problematic
>>> (especially on SATA drives where TRIM is a non-queued command):
>>>
>>> https://lwn.net/Articles/347511/
>>>
>> So the current problem with TRIM in ATA (and SATA) is that it
>> introduce delays? As long as it keeps your SSD in a good shape it's
>> still better than not having TRIM at all, right?
>
> Not quite.
>
> 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=
=2E
> Also, AFAIK currently TRIM is useless if the drives are behind a
> hardware raid controller anyway.
>
> My Corsair F60 (on a notebook) is actually MUCH SLOWER with -o discar=
d
> (i.e. writes capped at 100 iops)
>
> --
> Fajar
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs=
" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at =A0http://vger.kernel.org/majordomo-info.html
>



--=20
Caution: breathing may be hazardous to your health.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-07-10 22:34 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 [this message]
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

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=CAAeznTp-XB2eGarkfyVRASyLTULYLz0myPE+GN6TggrxPjv_YA@mail.gmail.com \
    --to=artafinde@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=list@fajar.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 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).