[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4BCF6831.7080506@redhat.com>
Date: Wed, 21 Apr 2010 17:03:45 -0400
From: Ric Wheeler <rwheeler@...hat.com>
To: sandeen@...hat.com
CC: Eric Sandeen <esandeen@...hat.com>,
Greg Freemyer <greg.freemyer@...il.com>,
Jeff Moyer <jmoyer@...hat.com>,
Mark Lord <kernel@...savvy.com>,
Lukas Czerner <lczerner@...hat.com>,
linux-ext4@...r.kernel.org, Edward Shishkin <eshishki@...hat.com>,
Christoph Hellwig <hch@...adead.org>
Subject: Re: [PATCH 2/2] Add batched discard support for ext4.
On 04/21/2010 05:01 PM, Eric Sandeen wrote:
> On 04/21/2010 03:44 PM, Greg Freemyer wrote:
>
>
>> Mark's benchmarks showed this as doable in seconds which seems like a
>> reasonable amount of time for a mount time operation.
>>
> All the other things aside, mount-time is interesting, but it's an
> infrequent operation, at least in my world. I think we need something
> that can be done runtime.
>
> For anything with uptime, I don't think it's acceptable to wait until
> the next mount to trim unused blocks.
>
> But as long as the mechanism can be called either at mount time and/or
> kicked off runtime somehow, I'm happy.
>
> -Eric
>
That makes sense to me. Most enterprise servers will go without
remounting a file system for (hopefully!) a very long time.
It is really important to keep in mind that this is not just a laptop
feature for laptop SSD's, this is also used by high end arrays and
*could* be useful for virt IO, etc as well :-)
ric
--
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