From: Mike Snitzer <snitzer@redhat.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Jan Kara <jack@suse.cz>, Jens Axboe <axboe@fb.com>,
dm-devel@redhat.com, Bart Van Assche <bart.vanassche@sandisk.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 0/2] Fix blkdev_issue_discard()
Date: Wed, 16 Dec 2015 00:12:23 -0500 [thread overview]
Message-ID: <20151216051223.GA11688@redhat.com> (raw)
In-Reply-To: <yq1k2ofunha.fsf@sermon.lab.mkp.net>
On Tue, Dec 15 2015 at 9:38pm -0500,
Martin K. Petersen <martin.petersen@oracle.com> wrote:
> >>>>> "Bart" == Bart Van Assche <bart.vanassche@sandisk.com> writes:
>
> Bart> Should the caller of blkdev_issue_discard() implement this or
> Bart> should this functionality be added in blkdev_issue_discard()
> Bart> itself ?
>
> I'm very much against dropping information in the ioctl/filesystem
> submission path. But I am not against having a helper function of some
> sort that DM and target could use to handle heads and tails.
>
> Right now DM does not handle this and I think it would be worthwhile to
> have. Mike, what are your requirements?
If the discard doesn't conform to the device's stacked discard limits
then yes the head and/or tail will get dropped on the floor.
Not sure why DM is being made the focal point on this. Are you thinking
specifically about DM-thinp and its discard_granularity? DM thinp
doesn't support partial thinp block discards -- so misaligned/partial
discards are dropped by DM thinp. There isn't a compelling case for
fixing this (by adding a bitset for each thinp block to support finer
grained discards) -- at least not that I'm aware of.
But I'm missing exactly what it is your helper function would do... and
yet you're asking me what my requirements are.. sorry ;)
next parent reply other threads:[~2015-12-16 5:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <567034B3.90104@sandisk.com>
[not found] ` <20151215154929.GA10785@lst.de>
[not found] ` <5670499E.9050501@sandisk.com>
[not found] ` <yq1k2ofunha.fsf@sermon.lab.mkp.net>
2015-12-16 5:12 ` Mike Snitzer [this message]
2015-12-16 8:44 ` [PATCH 0/2] Fix blkdev_issue_discard() Jan Kara
2015-12-16 9:02 ` Hannes Reinecke
2015-12-16 22:48 ` Martin K. Petersen
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=20151216051223.GA11688@redhat.com \
--to=snitzer@redhat.com \
--cc=axboe@fb.com \
--cc=bart.vanassche@sandisk.com \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=martin.petersen@oracle.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.