From: Alex Elsayed <eternaleye@gmail.com>
To: ceph-devel@vger.kernel.org
Subject: Re: DISCARD support in kernel driver
Date: Fri, 31 Jan 2014 18:36:36 -0800 [thread overview]
Message-ID: <lchmj8$vgv$1@ger.gmane.org> (raw)
In-Reply-To: 52EA1BE7.5030504@ovh.net
Jean-Tiare LE BIGOT wrote:
> Hi,
>
> I started to implement 'DISCARD' support in RBD kernel driver as
> described on http://tracker.ceph.com/issues/190
>
> This first (easy) step was to add at the end of
> drivers/block/rbd.c:rbd_init_disk
>
> /* Advertise discard support for aligned blocks */
> queue_flag_set_unlocked(QUEUE_FLAG_DISCARD, q);
> disk->queue->limits.discard_granularity = segment_size;
> disk->queue->limits.discard_alignment = segment_size;
>
> With this both 'mount -o discard' and 'fstrim' stopped to complain about
> missing 'DISCARD' support. Good !
>
> Next step was to add support on `rbd_request_fn` which I did (sort of).
> But here I'm stuck. If I understood well FS drivers uses `REQ_DISCARD`
> flag of `rq->cmd_flags` to notify the driver of the discard operation.
> But the problem is that (rq->cmd_flags & REQ_DISCARD) never appears to
> be set.
>
> I tried copying then removing large files, lots of small files, forcing
> fstrim. But I never got it. I must be missing something obvious but I
> can't manage to find what ? Do you have any clue what could be wrong ?
>
> Thanks,
>
Well, you can use the "blkdiscard" command to force a discard of an
arbitrary portion of a block device directly. You can used dd or ddrescue to
copy test patterns (maybe 0xFF) to and from RBD device, and use blkdiscard
to trim parts of that.
If that doesn't work, then the error must be elsewhere.
next prev parent reply other threads:[~2014-02-01 2:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 9:31 DISCARD support in kernel driver Jean-Tiare LE BIGOT
2014-01-30 15:24 ` Gregory Farnum
2014-01-30 15:27 ` Jean-Tiare LE BIGOT
2014-01-30 15:38 ` Gregory Farnum
2014-02-01 2:36 ` Alex Elsayed [this message]
2014-03-11 16:50 ` Sage Weil
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='lchmj8$vgv$1@ger.gmane.org' \
--to=eternaleye@gmail.com \
--cc=ceph-devel@vger.kernel.org \
/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.