[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <x49bp9yjjed.fsf@segfault.boston.devel.redhat.com>
Date: Fri, 23 Jul 2010 11:40:58 -0400
From: Jeff Moyer <jmoyer@...hat.com>
To: "Ted Ts'o" <tytso@....edu>
Cc: Lukas Czerner <lczerner@...hat.com>, eshishki@...hat.com,
rwheeler@...hat.com, linux-ext4@...r.kernel.org, sandeen@...hat.com
Subject: Re: Ext4: batched discard support - simplified version
"Ted Ts'o" <tytso@....edu> writes:
> On Fri, Jul 23, 2010 at 11:13:52AM -0400, Jeff Moyer wrote:
>>
>> I don't think so. In all of the configurations tested, I'm pretty sure
>> we saw a performance hit from doing the TRIMs right away. The queue
>> flush really hurts. Of course, I have no idea what you had in mind for
>> the amount of time in between batched discards.
>
> Sure, but not all the world is SATA-attached SSD's. I'm thinking in
> particular of PCIe-attached SSD's, where the TRIM command might be
> very fast indeed... I believe Ric Wheeler tells me you have TMS
> RamSan SSD's in house that you are testing? And of course those
> aren't the only PCIe-attached flash devices out there....
You are right, and we have to consider thinly provisioned luns, as well.
The only case I can think of where it makes sense to issue those
discards immediately is if you are running tight on allocated space in
your thinly provisioned lun. Aside from that, I'm not sure why you
would want to send those commands down with every journal commit,
instead of batched daily, for example. But, I can certainly understand
wanting to allow this flexibility.
Cheers,
Jeff
--
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
Powered by blists - more mailing lists