All of lore.kernel.org
 help / color / mirror / Atom feed
From: Busby <chaimvy@gmail.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: Does dm-thin support GC (garbage collection) ?
Date: Tue, 8 May 2012 13:01:29 +0800	[thread overview]
Message-ID: <CAJv3x-USC=8z7Kz_-p8uOiQkdE21Oe0isMeDOBKRc4semHbLCA@mail.gmail.com> (raw)
In-Reply-To: <20120507132242.GA27715@redhat.com>

Hi Mike,
            Thank you for your reply. Does the thin pool can reuse the
blocks that the thin-lun freed( like ssd 's discard/trim , the lun
will discard the blocks to the pool ). As the filesystem  creates a
file (3 G bytes big, etc.) will cause the block allocation of the thin
pool (thin lun), if delete the file, will the space(the blocks,3 G
bytes ,etc. ) dynamically be reused now (as we think thin-lun knows
the blocks delete by the FS )? or have to delete the thin-lun then the
space will be reused (just thin provision only once, not support block
reclamation from thin-lun to pool while lun is using )? I want to know
something about the 'block (page) reclamation' before my test :)
           Thanks.

Regards,
Busby


2012/5/7, Mike Snitzer <snitzer@redhat.com>:
> On Mon, May 07 2012 at  3:28am -0400,
> Busby <chaimvy@gmail.com> wrote:
>
>> Hi All,
>>          The dm-thin supports 'discard' now?Can I think this function
>> likes SSD's 'TRIM'? If it just discard the block mapped but not
>> remap(reallocate), the Pool's space will soon be used up . I want to
>> know whether it supports block reuse ( can use ext4 with '--discard'
>> test this? ) now or in the future.
>
> thinp discard support was added during upstream's most recent 3.4 merge
> window.  See:
> http://git.kernel.org/linus/104655fd4dcebd500
> http://git.kernel.org/linus/67e2e2b281812b5ca
>
> As you can see in the commit header for this last commit, you have
> control over how the discard (as issued by ext4, etc) is handled by
> thinp.  It should be noted that if the underlying storage does not
> support discard then the thin-pool will default to no_discard_passdown
> -- otherwise it does default to passing discards down to the underlying
> storage.
>
> But you'll need 2 late fixes for thinp issues that have been found
> during the 3.4-rcX development (these will be sent upstream shortly):
> http://www.redhat.com/archives/dm-devel/2012-April/msg00027.html
> http://www.redhat.com/archives/dm-devel/2012-April/msg00071.html
>
> (I'll bounce both of these patches to your email so you have them,
> please apply them before building/testing the latest 3.4-rcX kernel).
>
> Regards,
> Mike
>

  reply	other threads:[~2012-05-08  5:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07  7:28 Does dm-thin support GC (garbage collection) ? Busby
2012-05-07 13:22 ` Mike Snitzer
2012-05-08  5:01   ` Busby [this message]
2012-05-08  7:21     ` Busby
2012-05-08 10:30       ` Joe Thornber
2012-05-09  6:03         ` Busby
2012-05-09 13:47           ` Mike Snitzer

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='CAJv3x-USC=8z7Kz_-p8uOiQkdE21Oe0isMeDOBKRc4semHbLCA@mail.gmail.com' \
    --to=chaimvy@gmail.com \
    --cc=dm-devel@redhat.com \
    --cc=snitzer@redhat.com \
    /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.