linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: Toshi Kani <toshi.kani@hpe.com>,
	dm-devel@redhat.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-nvdimm@lists.01.org,
	linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2 5/7] dm: remove DM_TYPE_DAX_BIO_BASED dm_queue_mode
Date: Fri, 1 Jun 2018 18:04:43 -0400	[thread overview]
Message-ID: <20180601220443.GB18712@redhat.com> (raw)
In-Reply-To: <20180529195106.14268-6-ross.zwisler@linux.intel.com>

On Tue, May 29 2018 at  3:51pm -0400,
Ross Zwisler <ross.zwisler@linux.intel.com> wrote:

> The DM_TYPE_DAX_BIO_BASED dm_queue_mode was introduced to prevent DM
> devices that could possibly support DAX from transitioning into DM devices
> that cannot support DAX.
> 
> For example, the following transition will currently fail:
> 
>  dm-linear: [fsdax pmem][fsdax pmem] => [fsdax pmem][fsdax raw]
> 	      DM_TYPE_DAX_BIO_BASED       DM_TYPE_BIO_BASED
> 
> but these will both succeed:
> 
>  dm-linear: [fsdax pmem][brd ramdisk] => [fsdax pmem][fsdax raw]
>  	      DM_TYPE_DAX_BIO_BASED        DM_TYPE_BIO_BASED
> 

I fail to see how this succeeds given
drivers/md/dm-ioctl.c:is_valid_type() only allows transitions from:

DM_TYPE_BIO_BASED => DM_TYPE_DAX_BIO_BASED

>  dm-linear: [fsdax pmem][fsdax raw] => [fsdax pmem][fsdax pmem]
>  		DM_TYPE_BIO_BASED        DM_TYPE_DAX_BIO_BASED
> 
> This seems arbitrary, as really the choice on whether to use DAX happens at
> filesystem mount time.  There's no guarantee that the in the first case
> (double fsdax pmem) we were using the dax mount option with our file
> system.
> 
> Instead, get rid of DM_TYPE_DAX_BIO_BASED and all the special casing around
> it, and instead make the request queue's QUEUE_FLAG_DAX be our one source
> of truth.  If this is set, we can use DAX, and if not, not.  We keep this
> up to date in table_load() as the table changes.  As with regular block
> devices the filesystem will then know at mount time whether DAX is a
> supported mount option or not.

If you don't think you need this specialization that is fine.. but DM
devices supporting suspending (as part of table reloads) so is there any
risk that there will be inflight IO (say if someone did 'dmsetup suspend
--noflush').. and then upon reload the device type changed out from
under us.. anyway, I don't have all the PMEM DAX stuff paged back into
my head yet.

But this just seems like we really shouldn't be allowing the
transition from what was DM_TYPE_DAX_BIO_BASED back to DM_TYPE_BIO_BASED

Mike

> Signed-off-by: Ross Zwisler <ross.zwisler@linux.intel.com>
> ---
>  drivers/md/dm-ioctl.c         | 16 ++++++----------
>  drivers/md/dm-table.c         | 25 ++++++++++---------------
>  drivers/md/dm.c               |  2 --
>  include/linux/device-mapper.h |  8 ++++++--
>  4 files changed, 22 insertions(+), 29 deletions(-)
> 
> diff --git a/drivers/md/dm-ioctl.c b/drivers/md/dm-ioctl.c
> index 5acf77de5945..d1f86d0bb2d0 100644
> --- a/drivers/md/dm-ioctl.c
> +++ b/drivers/md/dm-ioctl.c
> @@ -1292,15 +1292,6 @@ static int populate_table(struct dm_table *table,
>  	return dm_table_complete(table);
>  }
>  
> -static bool is_valid_type(enum dm_queue_mode cur, enum dm_queue_mode new)
> -{
> -	if (cur == new ||
> -	    (cur == DM_TYPE_BIO_BASED && new == DM_TYPE_DAX_BIO_BASED))
> -		return true;
> -
> -	return false;
> -}
> -
>  static int table_load(struct file *filp, struct dm_ioctl *param, size_t param_size)
>  {
>  	int r;
> @@ -1343,12 +1334,17 @@ static int table_load(struct file *filp, struct dm_ioctl *param, size_t param_si
>  			DMWARN("unable to set up device queue for new table.");
>  			goto err_unlock_md_type;
>  		}
> -	} else if (!is_valid_type(dm_get_md_type(md), dm_table_get_type(t))) {
> +	} else if (dm_get_md_type(md) != dm_table_get_type(t)) {
>  		DMWARN("can't change device type after initial table load.");
>  		r = -EINVAL;
>  		goto err_unlock_md_type;
>  	}
>  
> +	if (dm_table_supports_dax(t))
> +		blk_queue_flag_set(QUEUE_FLAG_DAX, md->queue);
> +	else
> +		blk_queue_flag_clear(QUEUE_FLAG_DAX, md->queue);
> +
>  	dm_unlock_md_type(md);
>  
>  	/* stage inactive table */
> diff --git a/drivers/md/dm-table.c b/drivers/md/dm-table.c
> index 5bb994b012ca..ea5c4a1e6f5b 100644
> --- a/drivers/md/dm-table.c
> +++ b/drivers/md/dm-table.c
> @@ -866,7 +866,6 @@ EXPORT_SYMBOL(dm_consume_args);
>  static bool __table_type_bio_based(enum dm_queue_mode table_type)
>  {
>  	return (table_type == DM_TYPE_BIO_BASED ||
> -		table_type == DM_TYPE_DAX_BIO_BASED ||
>  		table_type == DM_TYPE_NVME_BIO_BASED);
>  }
>  
> @@ -888,7 +887,7 @@ static int device_supports_dax(struct dm_target *ti, struct dm_dev *dev,
>  	return bdev_dax_supported(dev->bdev, PAGE_SIZE);
>  }
>  
> -static bool dm_table_supports_dax(struct dm_table *t)
> +bool dm_table_supports_dax(struct dm_table *t)
>  {
>  	struct dm_target *ti;
>  	unsigned i;
> @@ -907,6 +906,7 @@ static bool dm_table_supports_dax(struct dm_table *t)
>  
>  	return true;
>  }
> +EXPORT_SYMBOL_GPL(dm_table_supports_dax);
>  
>  static bool dm_table_does_not_support_partial_completion(struct dm_table *t);
>  
> @@ -944,7 +944,6 @@ static int dm_table_determine_type(struct dm_table *t)
>  			/* possibly upgrade to a variant of bio-based */
>  			goto verify_bio_based;
>  		}
> -		BUG_ON(t->type == DM_TYPE_DAX_BIO_BASED);
>  		BUG_ON(t->type == DM_TYPE_NVME_BIO_BASED);
>  		goto verify_rq_based;
>  	}
> @@ -981,18 +980,14 @@ static int dm_table_determine_type(struct dm_table *t)
>  verify_bio_based:
>  		/* We must use this table as bio-based */
>  		t->type = DM_TYPE_BIO_BASED;
> -		if (dm_table_supports_dax(t) ||
> -		    (list_empty(devices) && live_md_type == DM_TYPE_DAX_BIO_BASED)) {
> -			t->type = DM_TYPE_DAX_BIO_BASED;
> -		} else {
> -			/* Check if upgrading to NVMe bio-based is valid or required */
> -			tgt = dm_table_get_immutable_target(t);
> -			if (tgt && !tgt->max_io_len && dm_table_does_not_support_partial_completion(t)) {
> -				t->type = DM_TYPE_NVME_BIO_BASED;
> -				goto verify_rq_based; /* must be stacked directly on NVMe (blk-mq) */
> -			} else if (list_empty(devices) && live_md_type == DM_TYPE_NVME_BIO_BASED) {
> -				t->type = DM_TYPE_NVME_BIO_BASED;
> -			}
> +
> +		/* Check if upgrading to NVMe bio-based is valid or required */
> +		tgt = dm_table_get_immutable_target(t);
> +		if (tgt && !tgt->max_io_len && dm_table_does_not_support_partial_completion(t)) {
> +			t->type = DM_TYPE_NVME_BIO_BASED;
> +			goto verify_rq_based; /* must be stacked directly on NVMe (blk-mq) */
> +		} else if (list_empty(devices) && live_md_type == DM_TYPE_NVME_BIO_BASED) {
> +			t->type = DM_TYPE_NVME_BIO_BASED;
>  		}
>  		return 0;
>  	}
> diff --git a/drivers/md/dm.c b/drivers/md/dm.c
> index 9728433362d1..0ce06fa292fd 100644
> --- a/drivers/md/dm.c
> +++ b/drivers/md/dm.c
> @@ -2192,7 +2192,6 @@ int dm_setup_md_queue(struct mapped_device *md, struct dm_table *t)
>  		}
>  		break;
>  	case DM_TYPE_BIO_BASED:
> -	case DM_TYPE_DAX_BIO_BASED:
>  		dm_init_normal_md_queue(md);
>  		blk_queue_make_request(md->queue, dm_make_request);
>  		break;
> @@ -2910,7 +2909,6 @@ struct dm_md_mempools *dm_alloc_md_mempools(struct mapped_device *md, enum dm_qu
>  
>  	switch (type) {
>  	case DM_TYPE_BIO_BASED:
> -	case DM_TYPE_DAX_BIO_BASED:
>  	case DM_TYPE_NVME_BIO_BASED:
>  		pool_size = max(dm_get_reserved_bio_based_ios(), min_pool_size);
>  		front_pad = roundup(per_io_data_size, __alignof__(struct dm_target_io)) + offsetof(struct dm_target_io, clone);
> diff --git a/include/linux/device-mapper.h b/include/linux/device-mapper.h
> index 31fef7c34185..cbf3d7e7ed33 100644
> --- a/include/linux/device-mapper.h
> +++ b/include/linux/device-mapper.h
> @@ -27,8 +27,7 @@ enum dm_queue_mode {
>  	DM_TYPE_BIO_BASED	 = 1,
>  	DM_TYPE_REQUEST_BASED	 = 2,
>  	DM_TYPE_MQ_REQUEST_BASED = 3,
> -	DM_TYPE_DAX_BIO_BASED	 = 4,
> -	DM_TYPE_NVME_BIO_BASED	 = 5,
> +	DM_TYPE_NVME_BIO_BASED	 = 4,
>  };
>  
>  typedef enum { STATUSTYPE_INFO, STATUSTYPE_TABLE } status_type_t;
> @@ -460,6 +459,11 @@ void dm_table_add_target_callbacks(struct dm_table *t, struct dm_target_callback
>   */
>  void dm_table_set_type(struct dm_table *t, enum dm_queue_mode type);
>  
> +/*
> + * Check to see if this target type and all table devices support DAX.
> + */
> +bool dm_table_supports_dax(struct dm_table *t);
> +
>  /*
>   * Finally call this to make the table ready for use.
>   */
> -- 
> 2.14.3
> 

  reply	other threads:[~2018-06-01 22:04 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29 19:50 [PATCH v2 0/7] Fix DM DAX handling Ross Zwisler
2018-05-29 19:51 ` [PATCH v2 1/7] fs: allow per-device dax status checking for filesystems Ross Zwisler
2018-05-29 19:51 ` [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns Ross Zwisler
2018-05-29 21:25   ` Darrick J. Wong
2018-05-29 22:01     ` Ross Zwisler
2018-05-31 19:13       ` Darrick J. Wong
2018-05-31 20:34         ` Ross Zwisler
2018-05-31 20:35         ` Dan Williams
2018-05-31 20:41         ` Ross Zwisler
2018-05-31 20:52         ` Mike Snitzer
2018-05-31 22:26           ` [dm-devel] " Darrick J. Wong
2018-06-01 20:59             ` Ross Zwisler
2018-06-01  1:26         ` Dave Chinner
2018-06-01  1:57           ` Dan Williams
2018-06-01  2:24             ` Dave Chinner
2018-06-01  4:02               ` Dan Williams
2018-06-03 22:20                 ` Dave Chinner
2018-06-04  0:25                   ` Dave Chinner
2018-06-04  1:48                     ` Dan Williams
2018-06-04 23:40                       ` Dan Williams
2018-06-05  0:33                         ` Mike Snitzer
2018-06-05  5:55                           ` Dave Chinner
2018-06-05  3:32                         ` Dan Williams
2018-05-29 19:51 ` [PATCH v2 3/7] dm: fix test for DAX device support Ross Zwisler
2018-06-01 20:19   ` Mike Snitzer
2018-06-01 20:46     ` Mike Snitzer
2018-06-01 21:11       ` Ross Zwisler
2018-06-01 21:16       ` Dan Williams
2018-05-29 19:51 ` [PATCH v2 4/7] dm: prevent DAX mounts if not supported Ross Zwisler
2018-06-01 21:55   ` Mike Snitzer
2018-06-04 23:15     ` Ross Zwisler
2018-06-20 15:17       ` Mike Snitzer
2018-06-25 19:20         ` Ross Zwisler
2018-05-29 19:51 ` [PATCH v2 5/7] dm: remove DM_TYPE_DAX_BIO_BASED dm_queue_mode Ross Zwisler
2018-06-01 22:04   ` Mike Snitzer [this message]
2018-06-04 23:24     ` Ross Zwisler
2018-06-04 23:49       ` Kani, Toshi
2018-06-05  0:46       ` Mike Snitzer
2018-06-06 17:24         ` Ross Zwisler
2018-06-06 22:29           ` Mike Snitzer
2018-05-29 19:51 ` [PATCH v2 6/7] dm-snap: remove unnecessary direct_access() stub Ross Zwisler
2018-05-29 19:51 ` [PATCH v2 7/7] dm-error: " Ross Zwisler

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=20180601220443.GB18712@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=ross.zwisler@linux.intel.com \
    --cc=toshi.kani@hpe.com \
    --subject='Re: [PATCH v2 5/7] dm: remove DM_TYPE_DAX_BIO_BASED dm_queue_mode' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).