From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?Mathias_Bur=C3=A9n?= Subject: Re: SSD - TRIM command Date: Tue, 22 Feb 2011 01:52:22 +0000 Message-ID: References: <4D62CF5F.6080007@cfl.rr.com> <20110222003610.GB29101@bounceswoosh.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: Sender: linux-raid-owner@vger.kernel.org To: Roberto Spadim Cc: "Eric D. Mudama" , Phillip Susi , David Brown , linux-raid@vger.kernel.org List-Id: linux-raid.ids On 22 February 2011 01:46, Roberto Spadim wrote: > if it make sense on ssd, harddisk make sense too, it's a block device > like ssd, the diference of ssd/harddisk? access time, > bytes(bits)/block, life time > bad block exist in ssd and harddisk, ssd can realloc online, some harddisks too > >> no, because the host may immediately write to a trim'd sector > yes, filesystem know where exists a unused sector > if device (harddisk/ssd) know and have a reallocation algorithm, it > can realloc without telling filesystem to do it (that's why TRIM is > interesting) > since today ssd use NAND (not NOR) the block size isn't 1 bit like a > harddisk head. trim for harddisk only make sense for badblock > reallocation > -------------------------- > getting back to the first question, can MD support trim? yes/no/not > now/some levels and layouts only? > -- > Roberto Spadim > Spadim Technology / SPAEmpresarial This explains a bit why trim is good for SSDs and has nothing to do with harddrives at all, since they use spinning platters and not chips. http://www.anandtech.com/show/2738/10 // Mathias