public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Zhang Boyang <zhangboyang.id@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
	linux-block@vger.kernel.org,
	Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	Jan Kara <jack@suse.cz>, Ming Lei <ming.lei@redhat.com>,
	Chaitanya Kulkarni <kch@nvidia.com>,
	Damien Le Moal <damien.lemoal@opensource.wdc.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 1/1] loop: introduce LO_FLAGS_NO_DEALLOC
Date: Tue, 9 Aug 2022 15:19:31 -0700	[thread overview]
Message-ID: <YvLdc8GtbZ968qF6@magnolia> (raw)
In-Reply-To: <20220806153022.83748-2-zhangboyang.id@gmail.com>

On Sat, Aug 06, 2022 at 11:30:22PM +0800, Zhang Boyang wrote:
> Previously, for file-backed loop devices, REQ_OP_DISCARD and
> REQ_OP_WRITE_ZEROES (without REQ_NOUNMAP) are implemented using
> fallocate(FALLOC_FL_PUNCH_HOLE), which will cause the underlying file to
> be sparse and disk space freed. The users have no choice to prevent this
> this from happening.
> 
> This patch introduces LO_FLAGS_NO_DEALLOC. With this flag set,
> REQ_OP_DISCARD and REQ_OP_WRITE_ZEROES are forced to use
> fallocate(FALLOC_FL_ZERO_RANGE). The disk space of underlying file is
> kept allocated. This is useful if users, for example, want to use a
> preallocated file as the backing file.

Considering that discard isn't required to do anything, why not
echo 0 | sudo tee /sys/block/loopX/queue/discard_max_bytes ?

--D

> Signed-off-by: Zhang Boyang <zhangboyang.id@gmail.com>
> ---
>  drivers/block/loop.c      | 17 +++++++++++++++--
>  include/uapi/linux/loop.h | 15 +++++++++++----
>  2 files changed, 26 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/block/loop.c b/drivers/block/loop.c
> index 084f9b8a0ba3..36bd9906a154 100644
> --- a/drivers/block/loop.c
> +++ b/drivers/block/loop.c
> @@ -483,11 +483,15 @@ static int do_req_filebacked(struct loop_device *lo, struct request *rq)
>  		 * write zeroes the range.  Otherwise, punch them out.
>  		 */
>  		return lo_fallocate(lo, rq, pos,
> -			(rq->cmd_flags & REQ_NOUNMAP) ?
> +			((rq->cmd_flags & REQ_NOUNMAP) ||
> +			 (lo->lo_flags & LO_FLAGS_NO_DEALLOC)) ?
>  				FALLOC_FL_ZERO_RANGE :
>  				FALLOC_FL_PUNCH_HOLE);
>  	case REQ_OP_DISCARD:
> -		return lo_fallocate(lo, rq, pos, FALLOC_FL_PUNCH_HOLE);
> +		return lo_fallocate(lo, rq, pos,
> +			(lo->lo_flags & LO_FLAGS_NO_DEALLOC) ?
> +				FALLOC_FL_ZERO_RANGE :
> +				FALLOC_FL_PUNCH_HOLE);
>  	case REQ_OP_WRITE:
>  		if (cmd->use_aio)
>  			return lo_rw_aio(lo, cmd, pos, WRITE);
> @@ -719,12 +723,20 @@ static ssize_t loop_attr_dio_show(struct loop_device *lo, char *buf)
>  	return sysfs_emit(buf, "%s\n", dio ? "1" : "0");
>  }
>  
> +static ssize_t loop_attr_no_dealloc_show(struct loop_device *lo, char *buf)
> +{
> +	int no_dealloc = (lo->lo_flags & LO_FLAGS_NO_DEALLOC);
> +
> +	return sysfs_emit(buf, "%s\n", no_dealloc ? "1" : "0");
> +}
> +
>  LOOP_ATTR_RO(backing_file);
>  LOOP_ATTR_RO(offset);
>  LOOP_ATTR_RO(sizelimit);
>  LOOP_ATTR_RO(autoclear);
>  LOOP_ATTR_RO(partscan);
>  LOOP_ATTR_RO(dio);
> +LOOP_ATTR_RO(no_dealloc);
>  
>  static struct attribute *loop_attrs[] = {
>  	&loop_attr_backing_file.attr,
> @@ -733,6 +745,7 @@ static struct attribute *loop_attrs[] = {
>  	&loop_attr_autoclear.attr,
>  	&loop_attr_partscan.attr,
>  	&loop_attr_dio.attr,
> +	&loop_attr_no_dealloc.attr,
>  	NULL,
>  };
>  
> diff --git a/include/uapi/linux/loop.h b/include/uapi/linux/loop.h
> index 6f63527dd2ed..91a0a8b1f298 100644
> --- a/include/uapi/linux/loop.h
> +++ b/include/uapi/linux/loop.h
> @@ -18,17 +18,24 @@ enum {
>  	LO_FLAGS_AUTOCLEAR	= 4,
>  	LO_FLAGS_PARTSCAN	= 8,
>  	LO_FLAGS_DIRECT_IO	= 16,
> +	LO_FLAGS_NO_DEALLOC	= 32,
>  };
>  
>  /* LO_FLAGS that can be set using LOOP_SET_STATUS(64) */
> -#define LOOP_SET_STATUS_SETTABLE_FLAGS (LO_FLAGS_AUTOCLEAR | LO_FLAGS_PARTSCAN)
> +#define LOOP_SET_STATUS_SETTABLE_FLAGS (LO_FLAGS_AUTOCLEAR		\
> +					| LO_FLAGS_PARTSCAN		\
> +					| LO_FLAGS_NO_DEALLOC)
>  
>  /* LO_FLAGS that can be cleared using LOOP_SET_STATUS(64) */
> -#define LOOP_SET_STATUS_CLEARABLE_FLAGS (LO_FLAGS_AUTOCLEAR)
> +#define LOOP_SET_STATUS_CLEARABLE_FLAGS (LO_FLAGS_AUTOCLEAR		\
> +					 | LO_FLAGS_NO_DEALLOC)
>  
>  /* LO_FLAGS that can be set using LOOP_CONFIGURE */
> -#define LOOP_CONFIGURE_SETTABLE_FLAGS (LO_FLAGS_READ_ONLY | LO_FLAGS_AUTOCLEAR \
> -				       | LO_FLAGS_PARTSCAN | LO_FLAGS_DIRECT_IO)
> +#define LOOP_CONFIGURE_SETTABLE_FLAGS (LO_FLAGS_READ_ONLY		\
> +				       | LO_FLAGS_AUTOCLEAR		\
> +				       | LO_FLAGS_PARTSCAN		\
> +				       | LO_FLAGS_DIRECT_IO		\
> +				       | LO_FLAGS_NO_DEALLOC)
>  
>  #include <asm/posix_types.h>	/* for __kernel_old_dev_t */
>  #include <linux/types.h>	/* for __u64 */
> -- 
> 2.30.2
> 

  reply	other threads:[~2022-08-09 22:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-06 15:30 [PATCH V2 0/1] loop: introduce LO_FLAGS_NO_DEALLOC Zhang Boyang
2022-08-06 15:30 ` [PATCH V2 1/1] " Zhang Boyang
2022-08-09 22:19   ` Darrick J. Wong [this message]
2022-08-10 11:00     ` Zhang Boyang
2022-08-11 11:40 ` Userspace support for LO_FLAGS_NO_DEALLOC (Re: [PATCH V2 0/1] loop: introduce LO_FLAGS_NO_DEALLOC) Zhang Boyang

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=YvLdc8GtbZ968qF6@magnolia \
    --to=djwong@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=kch@nvidia.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=ming.lei@redhat.com \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=zhangboyang.id@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox