[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YxFOS8fq8AeE5mkf@redhat.com>
Date: Thu, 1 Sep 2022 20:28:59 -0400
From: Mike Snitzer <snitzer@...hat.com>
To: Pankaj Raghav <p.raghav@...sung.com>
Cc: agk@...hat.com, snitzer@...nel.org, axboe@...nel.dk,
damien.lemoal@...nsource.wdc.com, hch@....de, pankydev8@...il.com,
Johannes.Thumshirn@....com, linux-block@...r.kernel.org,
dm-devel@...hat.com, hare@...e.de, jaegeuk@...nel.org,
linux-kernel@...r.kernel.org, matias.bjorling@....com,
gost.dev@...sung.com, bvanassche@....org,
linux-nvme@...ts.infradead.org
Subject: Re: [PATCH v12 12/13] dm: introduce DM_EMULATED_ZONES target type
On Tue, Aug 23 2022 at 8:18P -0400,
Pankaj Raghav <p.raghav@...sung.com> wrote:
> Introduce a new target type DM_EMULATED_ZONES for targets with
> a different number of sectors per zone (aka zone size) than the underlying
> device zone size.
>
> This target type is introduced as the existing zoned targets assume
> that the target and the underlying device have the same zone size.
> The new target: dm-po2zone will use this new target
> type as it emulates the zone boundary that is different from the
> underlying zoned device.
>
> Signed-off-by: Pankaj Raghav <p.raghav@...sung.com>
> Reviewed-by: Damien Le Moal <damien.lemoal@...nsource.wdc.com>
This patch's use of "target type" jargon isn't valid.
Please say "target feature flag" and rename DM_EMULATED_ZONES to
DM_TARGET_EMULATED_ZONES in the subject and header.
But, with those fixed:
Signed-off-by: Mike Snitzer <snitzer@...nel.org>
(fyi, I'll review patch 13, the dm-po2zone target, tomorrow)
Powered by blists - more mailing lists