From: Hannes Reinecke <hare@suse.de>
To: Damien Le Moal <damien.lemoal@wdc.com>,
dm-devel@redhat.com, Mike Snitzer <snitzer@redhat.com>,
linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH v2 06/11] dm: move zone related code to dm-zone.c
Date: Thu, 20 May 2021 07:54:42 +0200 [thread overview]
Message-ID: <00de9606-1ce2-0258-e376-2e3e29438c9d@suse.de> (raw)
In-Reply-To: <20210520042228.974083-7-damien.lemoal@wdc.com>
On 5/20/21 6:22 AM, Damien Le Moal wrote:
> Move core and table code used for zoned targets and conditionally
> defined with #ifdef CONFIG_BLK_DEV_ZONED to the new file dm-zone.c.
> This file is conditionally compiled depending on CONFIG_BLK_DEV_ZONED.
> The small helper dm_set_zones_restrictions() is introduced to
> initialize a mapped device request queue zone attributes in
> dm_table_set_restrictions().
>
> Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
> Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
> ---
> drivers/md/Makefile | 4 ++
> drivers/md/dm-table.c | 14 ++----
> drivers/md/dm-zone.c | 102 ++++++++++++++++++++++++++++++++++++++++++
> drivers/md/dm.c | 78 --------------------------------
> drivers/md/dm.h | 11 +++++
> 5 files changed, 120 insertions(+), 89 deletions(-)
> create mode 100644 drivers/md/dm-zone.c
> Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
next prev parent reply other threads:[~2021-05-20 5:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 4:22 [PATCH v2 00/11] dm: Improve zoned block device support Damien Le Moal
2021-05-20 4:22 ` [PATCH v2 01/11] block: improve handling of all zones reset operation Damien Le Moal
2021-05-20 5:49 ` Hannes Reinecke
2021-05-20 4:22 ` [PATCH v2 02/11] block: introduce bio zone helpers Damien Le Moal
2021-05-20 5:50 ` Hannes Reinecke
2021-05-20 4:22 ` [PATCH v2 03/11] block: introduce BIO_ZONE_WRITE_LOCKED bio flag Damien Le Moal
2021-05-20 5:52 ` Hannes Reinecke
2021-05-20 4:22 ` [PATCH v2 04/11] dm: Fix dm_accept_partial_bio() Damien Le Moal
2021-05-20 5:53 ` Hannes Reinecke
2021-05-20 4:22 ` [PATCH v2 05/11] dm: cleanup device_area_is_invalid() Damien Le Moal
2021-05-20 5:53 ` Hannes Reinecke
2021-05-20 4:22 ` [PATCH v2 06/11] dm: move zone related code to dm-zone.c Damien Le Moal
2021-05-20 5:54 ` Hannes Reinecke [this message]
2021-05-20 4:22 ` [PATCH v2 07/11] dm: Introduce dm_report_zones() Damien Le Moal
2021-05-20 5:56 ` Hannes Reinecke
2021-05-20 4:22 ` [PATCH v2 08/11] dm: Forbid requeue of writes to zones Damien Le Moal
2021-05-20 5:57 ` Hannes Reinecke
2021-05-20 4:22 ` [PATCH v2 09/11] dm: rearrange core declarations Damien Le Moal
2021-05-20 5:59 ` Hannes Reinecke
2021-05-20 4:22 ` [PATCH v2 10/11] dm: introduce zone append emulation Damien Le Moal
2021-05-20 6:10 ` Hannes Reinecke
2021-05-20 6:25 ` Damien Le Moal
2021-05-20 6:47 ` Hannes Reinecke
2021-05-20 6:57 ` Damien Le Moal
2021-05-20 4:22 ` [PATCH v2 11/11] dm crypt: Fix zoned block device support Damien Le Moal
2021-05-20 6:11 ` Hannes Reinecke
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=00de9606-1ce2-0258-e376-2e3e29438c9d@suse.de \
--to=hare@suse.de \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@wdc.com \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=snitzer@redhat.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;
as well as URLs for NNTP newsgroup(s).