From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: Christoph Hellwig <hch@lst.de>,
axboe@kernel.dk, martin.petersen@oracle.com,
philipp.reisner@linbit.com, lars.ellenberg@linbit.com,
target-devel@vger.kernel.org, haris.iqbal@ionos.com,
jinpu.wang@ionos.com, manoj@linux.ibm.com, mrochs@linux.ibm.com,
ukrishn@linux.ibm.com
Cc: linux-block@vger.kernel.org, dm-devel@redhat.com,
linux-scsi@vger.kernel.org, drbd-dev@lists.linbit.com
Subject: Re: [dm-devel] [PATCH 3/7] rnbd: drop WRITE_SAME support
Date: Wed, 9 Feb 2022 17:05:36 +0800 [thread overview]
Message-ID: <4f1565b2-0f83-0cfa-58bd-86d5dee48e51@linux.dev> (raw)
In-Reply-To: <20220209082828.2629273-4-hch@lst.de>
On 2/9/22 4:28 PM, Christoph Hellwig wrote:
> REQ_OP_WRITE_SAME was only ever submitted by the legacy Linux zeroing
> code, which has switched to use REQ_OP_WRITE_ZEROES long before rnbd was
> even merged.
>
> Signed-off-by: Christoph Hellwig<hch@lst.de>
> ---
> drivers/block/rnbd/rnbd-clt.c | 7 ++-----
> drivers/block/rnbd/rnbd-clt.h | 1 -
> drivers/block/rnbd/rnbd-proto.h | 6 ------
> drivers/block/rnbd/rnbd-srv.c | 3 +--
> 4 files changed, 3 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/block/rnbd/rnbd-clt.c b/drivers/block/rnbd/rnbd-clt.c
> index c08971de369fc..dc192d2738854 100644
> --- a/drivers/block/rnbd/rnbd-clt.c
> +++ b/drivers/block/rnbd/rnbd-clt.c
> @@ -82,7 +82,6 @@ static int rnbd_clt_set_dev_attr(struct rnbd_clt_dev *dev,
> dev->nsectors = le64_to_cpu(rsp->nsectors);
> dev->logical_block_size = le16_to_cpu(rsp->logical_block_size);
> dev->physical_block_size = le16_to_cpu(rsp->physical_block_size);
> - dev->max_write_same_sectors = le32_to_cpu(rsp->max_write_same_sectors);
> dev->max_discard_sectors = le32_to_cpu(rsp->max_discard_sectors);
> dev->discard_granularity = le32_to_cpu(rsp->discard_granularity);
> dev->discard_alignment = le32_to_cpu(rsp->discard_alignment);
> @@ -1359,8 +1358,6 @@ static void setup_request_queue(struct rnbd_clt_dev *dev)
> blk_queue_logical_block_size(dev->queue, dev->logical_block_size);
> blk_queue_physical_block_size(dev->queue, dev->physical_block_size);
> blk_queue_max_hw_sectors(dev->queue, dev->max_hw_sectors);
> - blk_queue_max_write_same_sectors(dev->queue,
> - dev->max_write_same_sectors);
>
> /*
> * we don't support discards to "discontiguous" segments
> @@ -1610,10 +1607,10 @@ struct rnbd_clt_dev *rnbd_clt_map_device(const char *sessname,
> }
>
> rnbd_clt_info(dev,
> - "map_device: Device mapped as %s (nsectors: %zu, logical_block_size: %d, physical_block_size: %d, max_write_same_sectors: %d, max_discard_sectors: %d, discard_granularity: %d, discard_alignment: %d, secure_discard: %d, max_segments: %d, max_hw_sectors: %d, rotational: %d, wc: %d, fua: %d)\n",
> + "map_device: Device mapped as %s (nsectors: %zu, logical_block_size: %d, physical_block_size: %d, max_discard_sectors: %d, discard_granularity: %d, discard_alignment: %d, secure_discard: %d, max_segments: %d, max_hw_sectors: %d, rotational: %d, wc: %d, fua: %d)\n",
> dev->gd->disk_name, dev->nsectors,
> dev->logical_block_size, dev->physical_block_size,
> - dev->max_write_same_sectors, dev->max_discard_sectors,
> + dev->max_discard_sectors,
> dev->discard_granularity, dev->discard_alignment,
> dev->secure_discard, dev->max_segments,
> dev->max_hw_sectors, dev->rotational, dev->wc, dev->fua);
> diff --git a/drivers/block/rnbd/rnbd-clt.h b/drivers/block/rnbd/rnbd-clt.h
> index 0c2cae7f39b9f..6946ba23d62e5 100644
> --- a/drivers/block/rnbd/rnbd-clt.h
> +++ b/drivers/block/rnbd/rnbd-clt.h
> @@ -122,7 +122,6 @@ struct rnbd_clt_dev {
> bool wc;
> bool fua;
> u32 max_hw_sectors;
> - u32 max_write_same_sectors;
> u32 max_discard_sectors;
> u32 discard_granularity;
> u32 discard_alignment;
I am planning to remove more members inside struct rnbd_clt_dev.
> diff --git a/drivers/block/rnbd/rnbd-proto.h b/drivers/block/rnbd/rnbd-proto.h
> index de5d5a8df81d7..3eb8b34bd1886 100644
> --- a/drivers/block/rnbd/rnbd-proto.h
> +++ b/drivers/block/rnbd/rnbd-proto.h
> @@ -249,9 +249,6 @@ static inline u32 rnbd_to_bio_flags(u32 rnbd_opf)
> case RNBD_OP_SECURE_ERASE:
> bio_opf = REQ_OP_SECURE_ERASE;
> break;
> - case RNBD_OP_WRITE_SAME:
> - bio_opf = REQ_OP_WRITE_SAME;
> - break;
> default:
> WARN(1, "Unknown RNBD type: %d (flags %d)\n",
> rnbd_op(rnbd_opf), rnbd_opf);
> @@ -284,9 +281,6 @@ static inline u32 rq_to_rnbd_flags(struct request *rq)
> case REQ_OP_SECURE_ERASE:
> rnbd_opf = RNBD_OP_SECURE_ERASE;
> break;
> - case REQ_OP_WRITE_SAME:
> - rnbd_opf = RNBD_OP_WRITE_SAME;
> - break;
> case REQ_OP_FLUSH:
> rnbd_opf = RNBD_OP_FLUSH;
> break;
> diff --git a/drivers/block/rnbd/rnbd-srv.c b/drivers/block/rnbd/rnbd-srv.c
> index 132e950685d59..0e6b5687f8321 100644
> --- a/drivers/block/rnbd/rnbd-srv.c
> +++ b/drivers/block/rnbd/rnbd-srv.c
> @@ -548,8 +548,7 @@ static void rnbd_srv_fill_msg_open_rsp(struct rnbd_msg_open_rsp *rsp,
> cpu_to_le16(rnbd_dev_get_max_segs(rnbd_dev));
> rsp->max_hw_sectors =
> cpu_to_le32(rnbd_dev_get_max_hw_sects(rnbd_dev));
> - rsp->max_write_same_sectors =
> - cpu_to_le32(bdev_write_same(rnbd_dev->bdev));
> + rsp->max_write_same_sectors = 0;
IIUC, I think we can delete max_write_same_sectors from rsp as well given
the earlier change in setup_request_queue and rnbd_clt_set_dev_attr.
Thanks,
Guoqing
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
WARNING: multiple messages have this Message-ID (diff)
From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: Christoph Hellwig <hch@lst.de>,
axboe@kernel.dk, martin.petersen@oracle.com,
philipp.reisner@linbit.com, lars.ellenberg@linbit.com,
target-devel@vger.kernel.org, haris.iqbal@ionos.com,
jinpu.wang@ionos.com, manoj@linux.ibm.com, mrochs@linux.ibm.com,
ukrishn@linux.ibm.com
Cc: linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
drbd-dev@lists.linbit.com, dm-devel@redhat.com
Subject: Re: [PATCH 3/7] rnbd: drop WRITE_SAME support
Date: Wed, 9 Feb 2022 17:05:36 +0800 [thread overview]
Message-ID: <4f1565b2-0f83-0cfa-58bd-86d5dee48e51@linux.dev> (raw)
In-Reply-To: <20220209082828.2629273-4-hch@lst.de>
On 2/9/22 4:28 PM, Christoph Hellwig wrote:
> REQ_OP_WRITE_SAME was only ever submitted by the legacy Linux zeroing
> code, which has switched to use REQ_OP_WRITE_ZEROES long before rnbd was
> even merged.
>
> Signed-off-by: Christoph Hellwig<hch@lst.de>
> ---
> drivers/block/rnbd/rnbd-clt.c | 7 ++-----
> drivers/block/rnbd/rnbd-clt.h | 1 -
> drivers/block/rnbd/rnbd-proto.h | 6 ------
> drivers/block/rnbd/rnbd-srv.c | 3 +--
> 4 files changed, 3 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/block/rnbd/rnbd-clt.c b/drivers/block/rnbd/rnbd-clt.c
> index c08971de369fc..dc192d2738854 100644
> --- a/drivers/block/rnbd/rnbd-clt.c
> +++ b/drivers/block/rnbd/rnbd-clt.c
> @@ -82,7 +82,6 @@ static int rnbd_clt_set_dev_attr(struct rnbd_clt_dev *dev,
> dev->nsectors = le64_to_cpu(rsp->nsectors);
> dev->logical_block_size = le16_to_cpu(rsp->logical_block_size);
> dev->physical_block_size = le16_to_cpu(rsp->physical_block_size);
> - dev->max_write_same_sectors = le32_to_cpu(rsp->max_write_same_sectors);
> dev->max_discard_sectors = le32_to_cpu(rsp->max_discard_sectors);
> dev->discard_granularity = le32_to_cpu(rsp->discard_granularity);
> dev->discard_alignment = le32_to_cpu(rsp->discard_alignment);
> @@ -1359,8 +1358,6 @@ static void setup_request_queue(struct rnbd_clt_dev *dev)
> blk_queue_logical_block_size(dev->queue, dev->logical_block_size);
> blk_queue_physical_block_size(dev->queue, dev->physical_block_size);
> blk_queue_max_hw_sectors(dev->queue, dev->max_hw_sectors);
> - blk_queue_max_write_same_sectors(dev->queue,
> - dev->max_write_same_sectors);
>
> /*
> * we don't support discards to "discontiguous" segments
> @@ -1610,10 +1607,10 @@ struct rnbd_clt_dev *rnbd_clt_map_device(const char *sessname,
> }
>
> rnbd_clt_info(dev,
> - "map_device: Device mapped as %s (nsectors: %zu, logical_block_size: %d, physical_block_size: %d, max_write_same_sectors: %d, max_discard_sectors: %d, discard_granularity: %d, discard_alignment: %d, secure_discard: %d, max_segments: %d, max_hw_sectors: %d, rotational: %d, wc: %d, fua: %d)\n",
> + "map_device: Device mapped as %s (nsectors: %zu, logical_block_size: %d, physical_block_size: %d, max_discard_sectors: %d, discard_granularity: %d, discard_alignment: %d, secure_discard: %d, max_segments: %d, max_hw_sectors: %d, rotational: %d, wc: %d, fua: %d)\n",
> dev->gd->disk_name, dev->nsectors,
> dev->logical_block_size, dev->physical_block_size,
> - dev->max_write_same_sectors, dev->max_discard_sectors,
> + dev->max_discard_sectors,
> dev->discard_granularity, dev->discard_alignment,
> dev->secure_discard, dev->max_segments,
> dev->max_hw_sectors, dev->rotational, dev->wc, dev->fua);
> diff --git a/drivers/block/rnbd/rnbd-clt.h b/drivers/block/rnbd/rnbd-clt.h
> index 0c2cae7f39b9f..6946ba23d62e5 100644
> --- a/drivers/block/rnbd/rnbd-clt.h
> +++ b/drivers/block/rnbd/rnbd-clt.h
> @@ -122,7 +122,6 @@ struct rnbd_clt_dev {
> bool wc;
> bool fua;
> u32 max_hw_sectors;
> - u32 max_write_same_sectors;
> u32 max_discard_sectors;
> u32 discard_granularity;
> u32 discard_alignment;
I am planning to remove more members inside struct rnbd_clt_dev.
> diff --git a/drivers/block/rnbd/rnbd-proto.h b/drivers/block/rnbd/rnbd-proto.h
> index de5d5a8df81d7..3eb8b34bd1886 100644
> --- a/drivers/block/rnbd/rnbd-proto.h
> +++ b/drivers/block/rnbd/rnbd-proto.h
> @@ -249,9 +249,6 @@ static inline u32 rnbd_to_bio_flags(u32 rnbd_opf)
> case RNBD_OP_SECURE_ERASE:
> bio_opf = REQ_OP_SECURE_ERASE;
> break;
> - case RNBD_OP_WRITE_SAME:
> - bio_opf = REQ_OP_WRITE_SAME;
> - break;
> default:
> WARN(1, "Unknown RNBD type: %d (flags %d)\n",
> rnbd_op(rnbd_opf), rnbd_opf);
> @@ -284,9 +281,6 @@ static inline u32 rq_to_rnbd_flags(struct request *rq)
> case REQ_OP_SECURE_ERASE:
> rnbd_opf = RNBD_OP_SECURE_ERASE;
> break;
> - case REQ_OP_WRITE_SAME:
> - rnbd_opf = RNBD_OP_WRITE_SAME;
> - break;
> case REQ_OP_FLUSH:
> rnbd_opf = RNBD_OP_FLUSH;
> break;
> diff --git a/drivers/block/rnbd/rnbd-srv.c b/drivers/block/rnbd/rnbd-srv.c
> index 132e950685d59..0e6b5687f8321 100644
> --- a/drivers/block/rnbd/rnbd-srv.c
> +++ b/drivers/block/rnbd/rnbd-srv.c
> @@ -548,8 +548,7 @@ static void rnbd_srv_fill_msg_open_rsp(struct rnbd_msg_open_rsp *rsp,
> cpu_to_le16(rnbd_dev_get_max_segs(rnbd_dev));
> rsp->max_hw_sectors =
> cpu_to_le32(rnbd_dev_get_max_hw_sects(rnbd_dev));
> - rsp->max_write_same_sectors =
> - cpu_to_le32(bdev_write_same(rnbd_dev->bdev));
> + rsp->max_write_same_sectors = 0;
IIUC, I think we can delete max_write_same_sectors from rsp as well given
the earlier change in setup_request_queue and rnbd_clt_set_dev_attr.
Thanks,
Guoqing
WARNING: multiple messages have this Message-ID (diff)
From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: Christoph Hellwig <hch@lst.de>,
axboe@kernel.dk, martin.petersen@oracle.com,
philipp.reisner@linbit.com, lars.ellenberg@linbit.com,
target-devel@vger.kernel.org, haris.iqbal@ionos.com,
jinpu.wang@ionos.com, manoj@linux.ibm.com, mrochs@linux.ibm.com,
ukrishn@linux.ibm.com
Cc: linux-block@vger.kernel.org, dm-devel@redhat.com,
linux-scsi@vger.kernel.org, drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] [PATCH 3/7] rnbd: drop WRITE_SAME support
Date: Wed, 9 Feb 2022 17:05:36 +0800 [thread overview]
Message-ID: <4f1565b2-0f83-0cfa-58bd-86d5dee48e51@linux.dev> (raw)
In-Reply-To: <20220209082828.2629273-4-hch@lst.de>
On 2/9/22 4:28 PM, Christoph Hellwig wrote:
> REQ_OP_WRITE_SAME was only ever submitted by the legacy Linux zeroing
> code, which has switched to use REQ_OP_WRITE_ZEROES long before rnbd was
> even merged.
>
> Signed-off-by: Christoph Hellwig<hch@lst.de>
> ---
> drivers/block/rnbd/rnbd-clt.c | 7 ++-----
> drivers/block/rnbd/rnbd-clt.h | 1 -
> drivers/block/rnbd/rnbd-proto.h | 6 ------
> drivers/block/rnbd/rnbd-srv.c | 3 +--
> 4 files changed, 3 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/block/rnbd/rnbd-clt.c b/drivers/block/rnbd/rnbd-clt.c
> index c08971de369fc..dc192d2738854 100644
> --- a/drivers/block/rnbd/rnbd-clt.c
> +++ b/drivers/block/rnbd/rnbd-clt.c
> @@ -82,7 +82,6 @@ static int rnbd_clt_set_dev_attr(struct rnbd_clt_dev *dev,
> dev->nsectors = le64_to_cpu(rsp->nsectors);
> dev->logical_block_size = le16_to_cpu(rsp->logical_block_size);
> dev->physical_block_size = le16_to_cpu(rsp->physical_block_size);
> - dev->max_write_same_sectors = le32_to_cpu(rsp->max_write_same_sectors);
> dev->max_discard_sectors = le32_to_cpu(rsp->max_discard_sectors);
> dev->discard_granularity = le32_to_cpu(rsp->discard_granularity);
> dev->discard_alignment = le32_to_cpu(rsp->discard_alignment);
> @@ -1359,8 +1358,6 @@ static void setup_request_queue(struct rnbd_clt_dev *dev)
> blk_queue_logical_block_size(dev->queue, dev->logical_block_size);
> blk_queue_physical_block_size(dev->queue, dev->physical_block_size);
> blk_queue_max_hw_sectors(dev->queue, dev->max_hw_sectors);
> - blk_queue_max_write_same_sectors(dev->queue,
> - dev->max_write_same_sectors);
>
> /*
> * we don't support discards to "discontiguous" segments
> @@ -1610,10 +1607,10 @@ struct rnbd_clt_dev *rnbd_clt_map_device(const char *sessname,
> }
>
> rnbd_clt_info(dev,
> - "map_device: Device mapped as %s (nsectors: %zu, logical_block_size: %d, physical_block_size: %d, max_write_same_sectors: %d, max_discard_sectors: %d, discard_granularity: %d, discard_alignment: %d, secure_discard: %d, max_segments: %d, max_hw_sectors: %d, rotational: %d, wc: %d, fua: %d)\n",
> + "map_device: Device mapped as %s (nsectors: %zu, logical_block_size: %d, physical_block_size: %d, max_discard_sectors: %d, discard_granularity: %d, discard_alignment: %d, secure_discard: %d, max_segments: %d, max_hw_sectors: %d, rotational: %d, wc: %d, fua: %d)\n",
> dev->gd->disk_name, dev->nsectors,
> dev->logical_block_size, dev->physical_block_size,
> - dev->max_write_same_sectors, dev->max_discard_sectors,
> + dev->max_discard_sectors,
> dev->discard_granularity, dev->discard_alignment,
> dev->secure_discard, dev->max_segments,
> dev->max_hw_sectors, dev->rotational, dev->wc, dev->fua);
> diff --git a/drivers/block/rnbd/rnbd-clt.h b/drivers/block/rnbd/rnbd-clt.h
> index 0c2cae7f39b9f..6946ba23d62e5 100644
> --- a/drivers/block/rnbd/rnbd-clt.h
> +++ b/drivers/block/rnbd/rnbd-clt.h
> @@ -122,7 +122,6 @@ struct rnbd_clt_dev {
> bool wc;
> bool fua;
> u32 max_hw_sectors;
> - u32 max_write_same_sectors;
> u32 max_discard_sectors;
> u32 discard_granularity;
> u32 discard_alignment;
I am planning to remove more members inside struct rnbd_clt_dev.
> diff --git a/drivers/block/rnbd/rnbd-proto.h b/drivers/block/rnbd/rnbd-proto.h
> index de5d5a8df81d7..3eb8b34bd1886 100644
> --- a/drivers/block/rnbd/rnbd-proto.h
> +++ b/drivers/block/rnbd/rnbd-proto.h
> @@ -249,9 +249,6 @@ static inline u32 rnbd_to_bio_flags(u32 rnbd_opf)
> case RNBD_OP_SECURE_ERASE:
> bio_opf = REQ_OP_SECURE_ERASE;
> break;
> - case RNBD_OP_WRITE_SAME:
> - bio_opf = REQ_OP_WRITE_SAME;
> - break;
> default:
> WARN(1, "Unknown RNBD type: %d (flags %d)\n",
> rnbd_op(rnbd_opf), rnbd_opf);
> @@ -284,9 +281,6 @@ static inline u32 rq_to_rnbd_flags(struct request *rq)
> case REQ_OP_SECURE_ERASE:
> rnbd_opf = RNBD_OP_SECURE_ERASE;
> break;
> - case REQ_OP_WRITE_SAME:
> - rnbd_opf = RNBD_OP_WRITE_SAME;
> - break;
> case REQ_OP_FLUSH:
> rnbd_opf = RNBD_OP_FLUSH;
> break;
> diff --git a/drivers/block/rnbd/rnbd-srv.c b/drivers/block/rnbd/rnbd-srv.c
> index 132e950685d59..0e6b5687f8321 100644
> --- a/drivers/block/rnbd/rnbd-srv.c
> +++ b/drivers/block/rnbd/rnbd-srv.c
> @@ -548,8 +548,7 @@ static void rnbd_srv_fill_msg_open_rsp(struct rnbd_msg_open_rsp *rsp,
> cpu_to_le16(rnbd_dev_get_max_segs(rnbd_dev));
> rsp->max_hw_sectors =
> cpu_to_le32(rnbd_dev_get_max_hw_sects(rnbd_dev));
> - rsp->max_write_same_sectors =
> - cpu_to_le32(bdev_write_same(rnbd_dev->bdev));
> + rsp->max_write_same_sectors = 0;
IIUC, I think we can delete max_write_same_sectors from rsp as well given
the earlier change in setup_request_queue and rnbd_clt_set_dev_attr.
Thanks,
Guoqing
next prev parent reply other threads:[~2022-02-09 9:15 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 8:28 [dm-devel] remove REQ_OP_WRITE_SAME v2 Christoph Hellwig
2022-02-09 8:28 ` [Drbd-dev] " Christoph Hellwig
2022-02-09 8:28 ` Christoph Hellwig
2022-02-09 8:28 ` [dm-devel] [PATCH 1/7] cxlflash: query write_zeroes limit for zeroing Christoph Hellwig
2022-02-09 8:28 ` [Drbd-dev] " Christoph Hellwig
2022-02-09 8:28 ` Christoph Hellwig
2022-02-09 8:43 ` [dm-devel] " Chaitanya Kulkarni
2022-02-09 8:43 ` [Drbd-dev] " Chaitanya Kulkarni
2022-02-09 8:43 ` Chaitanya Kulkarni
2022-02-09 8:28 ` [dm-devel] [PATCH 2/7] drbd: drop REQ_OP_WRITE_SAME support Christoph Hellwig
2022-02-09 8:28 ` [Drbd-dev] " Christoph Hellwig
2022-02-09 8:28 ` Christoph Hellwig
2022-02-09 8:28 ` [dm-devel] [PATCH 3/7] rnbd: drop WRITE_SAME support Christoph Hellwig
2022-02-09 8:28 ` [Drbd-dev] " Christoph Hellwig
2022-02-09 8:28 ` Christoph Hellwig
2022-02-09 8:44 ` [dm-devel] " Chaitanya Kulkarni
2022-02-09 8:44 ` [Drbd-dev] " Chaitanya Kulkarni
2022-02-09 8:44 ` Chaitanya Kulkarni
2022-02-09 9:05 ` Guoqing Jiang [this message]
2022-02-09 9:05 ` [Drbd-dev] " Guoqing Jiang
2022-02-09 9:05 ` Guoqing Jiang
2022-02-09 9:13 ` [dm-devel] " Jinpu Wang
2022-02-09 9:13 ` [Drbd-dev] " Jinpu Wang
2022-02-09 9:13 ` Jinpu Wang
2022-02-09 9:21 ` [dm-devel] " Guoqing Jiang
2022-02-09 9:21 ` [Drbd-dev] " Guoqing Jiang
2022-02-09 9:21 ` Guoqing Jiang
2022-02-09 10:16 ` [dm-devel] " Jinpu Wang
2022-02-09 10:16 ` [Drbd-dev] " Jinpu Wang
2022-02-09 10:16 ` Jinpu Wang
2022-02-09 14:04 ` [dm-devel] " Christoph Hellwig
2022-02-09 14:04 ` [Drbd-dev] " Christoph Hellwig
2022-02-09 14:04 ` Christoph Hellwig
2022-02-09 14:08 ` [dm-devel] " Jinpu Wang
2022-02-09 14:08 ` [Drbd-dev] " Jinpu Wang
2022-02-09 14:08 ` Jinpu Wang
2022-02-09 8:28 ` [dm-devel] [PATCH 4/7] sd: remove write same support Christoph Hellwig
2022-02-09 8:28 ` [Drbd-dev] " Christoph Hellwig
2022-02-09 8:28 ` Christoph Hellwig
2022-02-09 8:45 ` [dm-devel] " Chaitanya Kulkarni
2022-02-09 8:45 ` [Drbd-dev] " Chaitanya Kulkarni
2022-02-09 8:45 ` Chaitanya Kulkarni
2022-02-09 8:28 ` [dm-devel] [PATCH 5/7] md: drop WRITE_SAME support Christoph Hellwig
2022-02-09 8:28 ` [Drbd-dev] " Christoph Hellwig
2022-02-09 8:28 ` Christoph Hellwig
2022-02-09 8:28 ` [dm-devel] [PATCH 6/7] dm: remove write same support Christoph Hellwig
2022-02-09 8:28 ` [Drbd-dev] " Christoph Hellwig
2022-02-09 8:28 ` Christoph Hellwig
2022-02-16 18:45 ` [dm-devel] " Mike Snitzer
2022-02-16 18:45 ` [Drbd-dev] " Mike Snitzer
2022-02-16 18:45 ` Mike Snitzer
2022-02-09 8:28 ` [dm-devel] [PATCH 7/7] block: remove REQ_OP_WRITE_SAME support Christoph Hellwig
2022-02-09 8:28 ` [Drbd-dev] " Christoph Hellwig
2022-02-09 8:28 ` Christoph Hellwig
2022-02-09 8:46 ` [dm-devel] " Chaitanya Kulkarni
2022-02-09 8:46 ` [Drbd-dev] " Chaitanya Kulkarni
2022-02-09 8:46 ` Chaitanya Kulkarni
2022-02-20 1:44 ` [dm-devel] " Martin K. Petersen
2022-02-20 1:44 ` [Drbd-dev] " Martin K. Petersen
2022-02-20 1:44 ` Martin K. Petersen
2022-02-22 7:38 ` [dm-devel] " Christoph Hellwig
2022-02-22 7:38 ` [Drbd-dev] " Christoph Hellwig
2022-02-22 7:38 ` Christoph Hellwig
2022-02-23 1:58 ` [dm-devel] " Martin K. Petersen
2022-02-23 1:58 ` [Drbd-dev] " Martin K. Petersen
2022-02-23 1:58 ` Martin K. Petersen
2022-02-09 8:47 ` [dm-devel] remove REQ_OP_WRITE_SAME v2 Chaitanya Kulkarni
2022-02-09 8:47 ` [Drbd-dev] " Chaitanya Kulkarni
2022-02-09 8:47 ` Chaitanya Kulkarni
2022-02-09 18:00 ` [dm-devel] " Martin K. Petersen
2022-02-09 18:00 ` [Drbd-dev] " Martin K. Petersen
2022-02-09 18:00 ` Martin K. Petersen
2022-02-10 5:51 ` [dm-devel] " Christoph Hellwig
2022-02-10 5:51 ` [Drbd-dev] " Christoph Hellwig
2022-02-10 5:51 ` Christoph Hellwig
2022-02-17 3:07 ` [dm-devel] " Jens Axboe
2022-02-17 3:07 ` [Drbd-dev] " Jens Axboe
2022-02-17 3:07 ` Jens Axboe
2022-02-17 6:43 ` [dm-devel] " Christoph Hellwig
2022-02-17 6:43 ` [Drbd-dev] " Christoph Hellwig
2022-02-17 6:43 ` Christoph Hellwig
2022-02-18 4:27 ` [dm-devel] " Martin K. Petersen
2022-02-18 4:27 ` [Drbd-dev] " Martin K. Petersen
2022-02-18 4:27 ` Martin K. Petersen
2022-02-19 23:33 ` [dm-devel] " Martin K. Petersen
2022-02-19 23:33 ` [Drbd-dev] " Martin K. Petersen
2022-02-19 23:33 ` Martin K. Petersen
2022-02-28 3:43 ` [dm-devel] " Martin K. Petersen
2022-02-28 3:43 ` [Drbd-dev] " Martin K. Petersen
2022-02-28 3:43 ` 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=4f1565b2-0f83-0cfa-58bd-86d5dee48e51@linux.dev \
--to=guoqing.jiang@linux.dev \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=drbd-dev@lists.linbit.com \
--cc=haris.iqbal@ionos.com \
--cc=hch@lst.de \
--cc=jinpu.wang@ionos.com \
--cc=lars.ellenberg@linbit.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=manoj@linux.ibm.com \
--cc=martin.petersen@oracle.com \
--cc=mrochs@linux.ibm.com \
--cc=philipp.reisner@linbit.com \
--cc=target-devel@vger.kernel.org \
--cc=ukrishn@linux.ibm.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.