All of lore.kernel.org
 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: Mon, 11 Jul 2011 08:02:43 +0100	[thread overview]
Message-ID: <CAAeznTrou2TOTGtvKDBudQqaTmHjzNoV8AUug3Uw2uUMJJjJVg@mail.gmail.com> (raw)
In-Reply-To: <CAG1y0sf=8PdiXwavma7Vc40td_mpEt+uZJBto+OLW_B+M8QVEQ@mail.gmail.com>

On Mon, Jul 11, 2011 at 7:04 AM, Fajar A. Nugraha <list@fajar.net> wrot=
e:
> On Mon, Jul 11, 2011 at 5:34 AM, Leonidas Spyropoulos
> <artafinde@gmail.com> wrote:
>> So any clues for the intel 320 series? I think it doesn't use compre=
ssion.
>
> At this point your best bet is to try it yourself and see. If it
> doesn't result in poor performance, then keep on using "-o discard".
Could you propose me any tools available for measuring performance?

I only know iozone and tunefs -t parameter.
>
> --
> Fajar
>
>>
>> On Sun, Jul 10, 2011 at 10:59 PM, Fajar A. Nugraha <list@fajar.net> =
wrote:
>>> 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> =
wrote:
>>>>> 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 speci=
al.
>>> 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 disc=
ard
>>> (i.e. writes capped at 100 iops)
> --
> 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-11  7:02 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 [this message]
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=CAAeznTrou2TOTGtvKDBudQqaTmHjzNoV8AUug3Uw2uUMJJjJVg@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 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.