From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Pankaj Raghav <p.raghav@samsung.com>, "hch@lst.de" <hch@lst.de>,
"agk@redhat.com" <agk@redhat.com>,
"damien.lemoal@opensource.wdc.com"
<damien.lemoal@opensource.wdc.com>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"snitzer@kernel.org" <snitzer@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Johannes.Thumshirn@wdc.com" <Johannes.Thumshirn@wdc.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"pankydev8@gmail.com" <pankydev8@gmail.com>,
"matias.bjorling@wdc.com" <matias.bjorling@wdc.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"gost.dev@samsung.com" <gost.dev@samsung.com>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
"hare@suse.de" <hare@suse.de>,
"jaegeuk@kernel.org" <jaegeuk@kernel.org>,
Luis Chamberlain <mcgrof@kernel.org>
Subject: Re: [PATCH v13 07/13] zonefs: allow non power of 2 zoned devices
Date: Wed, 14 Sep 2022 17:17:27 +0000 [thread overview]
Message-ID: <9595fdee-44b3-e210-a650-3c67875bef22@nvidia.com> (raw)
In-Reply-To: <20220912082204.51189-8-p.raghav@samsung.com>
On 9/12/2022 1:21 AM, Pankaj Raghav wrote:
> The zone size shift variable is useful only if the zone sizes are known
> to be power of 2. Remove that variable and use generic helpers from
> block layer to calculate zone index in zonefs.
>
> Acked-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
> Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
> Signed-off-by: Pankaj Raghav <p.raghav@samsung.com>
> ---
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
next prev parent reply other threads:[~2022-09-14 17:17 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220912082205eucas1p1e5fb1acfb0b2a2fe6261520ace90c883@eucas1p1.samsung.com>
2022-09-12 8:21 ` [PATCH v13 00/13] support zoned block devices with non-power-of-2 zone sizes Pankaj Raghav
2022-09-12 8:21 ` [PATCH v13 01/13] block: make bdev_nr_zones and disk_zone_no generic for npo2 zone size Pankaj Raghav
2022-09-12 10:03 ` Johannes Thumshirn
2022-09-14 17:19 ` Chaitanya Kulkarni
2022-09-12 8:21 ` [PATCH v13 02/13] block: rearrange bdev_{is_zoned,zone_sectors,get_queue} helper in blkdev.h Pankaj Raghav
2022-09-12 10:03 ` Johannes Thumshirn
2022-09-14 17:19 ` Chaitanya Kulkarni
2022-09-12 8:21 ` [PATCH v13 03/13] block: allow blk-zoned devices to have non-power-of-2 zone size Pankaj Raghav
2022-09-12 10:04 ` Johannes Thumshirn
2022-09-12 8:21 ` [PATCH v13 04/13] nvmet: Allow ZNS target to support non-power_of_2 zone sizes Pankaj Raghav
2022-09-14 17:16 ` Chaitanya Kulkarni
2022-09-12 8:21 ` [PATCH v13 05/13] nvme: zns: Allow ZNS drives that have non-power_of_2 zone size Pankaj Raghav
2022-09-14 17:16 ` Chaitanya Kulkarni
2022-09-12 8:21 ` [PATCH v13 06/13] null_blk: allow zoned devices with non power-of-2 zone sizes Pankaj Raghav
2022-09-12 10:06 ` Johannes Thumshirn
2022-09-14 17:17 ` Chaitanya Kulkarni
2022-09-12 8:21 ` [PATCH v13 07/13] zonefs: allow non power of 2 zoned devices Pankaj Raghav
2022-09-12 10:07 ` Johannes Thumshirn
2022-09-14 17:17 ` Chaitanya Kulkarni [this message]
2022-09-12 8:21 ` [PATCH v13 08/13] dm-zoned: ensure only power of 2 zone sizes are allowed Pankaj Raghav
2022-09-12 10:07 ` Johannes Thumshirn
2022-09-12 8:22 ` [PATCH v13 09/13] dm-zone: use generic helpers to calculate offset from zone start Pankaj Raghav
2022-09-12 10:08 ` Johannes Thumshirn
2022-09-12 8:22 ` [PATCH v13 10/13] dm-table: allow zoned devices with non power-of-2 zone sizes Pankaj Raghav
2022-09-12 10:08 ` Johannes Thumshirn
2022-09-12 8:22 ` [PATCH v13 11/13] dm: call dm_zone_endio after the target endio callback for zoned devices Pankaj Raghav
2022-09-12 8:22 ` [PATCH v13 12/13] dm: introduce DM_EMULATED_ZONES target feature flag Pankaj Raghav
2022-09-12 8:22 ` [PATCH v13 13/13] dm: add power-of-2 target for zoned devices with non power-of-2 zone sizes Pankaj Raghav
2022-09-14 16:52 ` Mike Snitzer
2022-09-14 19:16 ` Pankaj Raghav
2022-09-16 17:57 ` Pankaj Raghav
2022-09-16 18:04 ` Mike Snitzer
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=9595fdee-44b3-e210-a650-3c67875bef22@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=dm-devel@redhat.com \
--cc=gost.dev@samsung.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jaegeuk@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=matias.bjorling@wdc.com \
--cc=mcgrof@kernel.org \
--cc=p.raghav@samsung.com \
--cc=pankydev8@gmail.com \
--cc=snitzer@kernel.org \
/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