linux-ext4 - Re: Is TRIM/DISCARD going to be a performance problem?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <f3177b9e0905110930p3fe180b0nbd26bd24f17b068e@mail.gmail.com>
Date:	Mon, 11 May 2009 10:30:09 -0600
From:	Chris Worley <worleys@...il.com>
To:	Jörn Engel <joern@...fs.org>
Cc:	linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org
Subject: Re: Is TRIM/DISCARD going to be a performance problem?

On Mon, May 11, 2009 at 4:06 AM, Jörn Engel <joern@...fs.org> wrote:
>
> I am not sure about this part.  So far Intel has been the only party to
> release any information about their dark-grey box.  All other boxes are
> still solid black.  And until I'm told otherwise I'd consider them to be
> stupid devices that use erase block size as trim granularity.

Consider yourself informed otherwise: I can't imagine a vendor
brain-dead enough to require that.  It's the same thing as requiring
that the only way to re-write an LBA is to re-write all LBA's in the
same erase block.

Note that Fusion-io supports "discard" in their released 1.2.5 drivers.

Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html