All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bart.vanassche@sandisk.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: James Bottomley <jejb@linux.vnet.ibm.com>,
	Jens Axboe <axboe@fb.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"lsf@lists.linux-foundation.org" <lsf@lists.linux-foundation.org>,
	"Darrick J. Wong" <darrick.wong@oracle.com>
Subject: Re: LSF/MM Schedule and improving discard support
Date: Wed, 13 Apr 2016 09:29:09 -0700	[thread overview]
Message-ID: <570E73D5.3010502@sandisk.com> (raw)
In-Reply-To: <yq11t69wkcl.fsf@sermon.lab.mkp.net>

On 04/13/2016 09:21 AM, Martin K. Petersen wrote:
> From a filesystem/ioctl perspective, BLKDISCARD is a hint. We should not be
> rounding off or aligning anything.

Hello Martin,

Today if a BLKDISCARD ioctl passes a non-aligned start and/or end sector 
to the kernel then the block layer will submit invalid (non-aligned) 
REQ_DISCARD requests to the block driver the ioctl applies to. This is 
not acceptable. Does the above mean that you are proposing to fail such 
BLKDISCARD ioctls with an error code?

Thanks,

Bart.


  reply	other threads:[~2016-04-13 16:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07 15:39 LSF/MM Schedule and improving discard support Bart Van Assche
2016-04-07 15:51 ` James Bottomley
2016-04-13 15:57   ` Bart Van Assche
2016-04-13 16:21     ` Martin K. Petersen
2016-04-13 16:29       ` Bart Van Assche [this message]
2016-04-13 16:43         ` [Lsf] " Martin K. Petersen
2016-04-13 16:57           ` Bart Van Assche
2016-04-13 17:13             ` Martin K. Petersen
2016-04-13 16:51         ` James Bottomley
2016-04-13 17:30           ` Darrick J. Wong
2016-04-13 22:04             ` Douglas Gilbert

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=570E73D5.3010502@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --cc=axboe@fb.com \
    --cc=darrick.wong@oracle.com \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsf@lists.linux-foundation.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.