From: Pankaj Raghav <p.raghav@samsung.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
<snitzer@kernel.org>, <axboe@kernel.dk>, <hch@lst.de>,
<agk@redhat.com>
Cc: <linux-block@vger.kernel.org>, <Johannes.Thumshirn@wdc.com>,
<bvanassche@acm.org>, <matias.bjorling@wdc.com>, <hare@suse.de>,
<gost.dev@samsung.com>, <linux-nvme@lists.infradead.org>,
<jaegeuk@kernel.org>, <pankydev8@gmail.com>,
<linux-kernel@vger.kernel.org>, <dm-devel@redhat.com>,
Damien Le Moal <damien.lemoal@wdc.com>,
Joel Granados <j.granados@samsung.com>
Subject: Re: [PATCH v10 13/13] dm: add power-of-2 target for zoned devices with non power-of-2 zone sizes
Date: Mon, 15 Aug 2022 15:38:29 +0200 [thread overview]
Message-ID: <b98ab80d-1bc0-a378-d438-09ef8b375836@samsung.com> (raw)
In-Reply-To: <bb4ab1f2-7e16-15a7-58b1-d37f6f3822fd@opensource.wdc.com>
Hi Damien,
>> +static int dm_po2z_map_read_emulated_area(struct dm_po2z_target *dmh,
>> + struct bio *bio)
>
> This really should be called dm_po2z_handle_read() since it handles both cases
> of read commands, with and without the accept partial. Note that this is
> retesting the need for a split after that was already tested in dm_po2z_map()
> with bio_across_emulated_zone_area(). So the code should be better organized to
> avoid that repetition.
>
> You can simplify the code by having bio_across_emulated_zone_area() return 0 for
> a bio that does not cross the zone capacity and return the number of sectors up
> to the zone capacity from the bio start if there is a cross. That value can then
The offset will also be zero if the BIO starts at the zone capacity and
dm_po2z_map will assume that the bio did not cross the emulated zone boundary.
> be used to call dm_accept_partial_bio() directly in dm_po2z_map() for read
> commands. That will make this function much simpler and essentially turn it into
> dm_po2z_read_zeroes().
>
>> +{
What about something like this? We have one function:
bio_in_emulated_zone_area() that checks if a BIO is partly or completely in the
emulated zone area and also returns the offset from bio to the emulated zone
boundary (zone capacity of the device).
/**
* bio_in_emulated_zone_area - check if bio is in the emulated zone area
* @dmh: pozone target data
* @bio: bio
* @offset: bio offset to emulated zone boundary
*
* Check if a @bio is partly or completely in the emulated zone area. If the
* @bio is partly in the emulated zone area, @offset
* can be used to split the @bio across the emulated zone boundary. @offset
* will be negative if the @bio completely lies in the emulated area.
* */
static bool bio_in_emulated_zone_area(struct dm_po2z_target *dmh,
struct bio *bio, int *offset)
{
unsigned int zone_idx = po2_zone_no(dmh, bio->bi_iter.bi_sector);
sector_t nr_sectors = bio->bi_iter.bi_size >> SECTOR_SHIFT;
sector_t relative_sect_in_zone =
bio->bi_iter.bi_sector - (zone_idx << dmh->zone_size_po2_shift);
*offset = dmh->zone_size - relative_sect_in_zone;
return (relative_sect_in_zone + nr_sectors) > dmh->zone_size;
}
static int dm_po2z_read_zeroes(struct bio *bio)
{
zero_fill_bio(bio);
bio_endio(bio);
return DM_MAPIO_SUBMITTED;
}
static int dm_po2z_remap_sector(struct dm_po2z_target *dmh, struct bio *bio)
{
bio->bi_iter.bi_sector =
target_to_device_sect(dmh, bio->bi_iter.bi_sector);
return DM_MAPIO_REMAPPED;
}
static int dm_po2z_map(struct dm_target *ti, struct bio *bio)
{
struct dm_po2z_target *dmh = ti->private;
bio_set_dev(bio, dmh->dev->bdev);
if (bio_sectors(bio) || op_is_zone_mgmt(bio_op(bio))) {
int split_io_pos;
if (!bio_in_emulated_zone_area(dmh, bio, &split_io_pos)) {
return dm_po2z_remap_sector(dmh, bio);
}
/*
* Read operation on the emulated zone area (between zone capacity
* and zone size) will fill the bio with zeroes. Any other operation
* in the emulated area should return an error.
*/
if (bio_op(bio) == REQ_OP_READ) {
if (split_io_pos > 0) {
dm_accept_partial_bio(bio, split_io_pos);
return dm_po2z_remap_sector(dmh, bio);
}
return dm_po2z_read_zeroes(bio);
}
return DM_MAPIO_KILL;
}
return DM_MAPIO_REMAPPED;
}
Let me know what you think.
next prev parent reply other threads:[~2022-08-15 13:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220811143044eucas1p2cb35a5c247788689aeebf2bc8eb9f5df@eucas1p2.samsung.com>
2022-08-11 14:30 ` [PATCH v10 00/13] support zoned block devices with non-power-of-2 zone sizes Pankaj Raghav
2022-08-11 14:30 ` [PATCH v10 01/13] block: make bdev_nr_zones and disk_zone_no generic for npo2 zone size Pankaj Raghav
2022-08-11 14:30 ` [PATCH v10 02/13] block:rearrange bdev_{is_zoned,zone_sectors,get_queue} helpers in blkdev.h Pankaj Raghav
2022-08-11 20:21 ` Damien Le Moal
2022-08-11 14:30 ` [PATCH v10 03/13] block: allow blk-zoned devices to have non-power-of-2 zone size Pankaj Raghav
2022-08-11 14:30 ` [PATCH v10 04/13] nvmet: Allow ZNS target to support non-power_of_2 zone sizes Pankaj Raghav
2022-08-11 14:30 ` [PATCH v10 05/13] nvme: zns: Allow ZNS drives that have non-power_of_2 zone size Pankaj Raghav
2022-08-16 21:14 ` Keith Busch
2022-08-17 7:28 ` Pankaj Raghav
2022-08-11 14:30 ` [PATCH v10 06/13] null_blk: allow zoned devices with non power-of-2 zone sizes Pankaj Raghav
2022-08-11 14:30 ` [PATCH v10 07/13] zonefs: allow non power of 2 zoned devices Pankaj Raghav
2022-08-11 14:30 ` [PATCH v10 08/13] dm-zoned: ensure only power of 2 zone sizes are allowed Pankaj Raghav
2022-08-11 14:30 ` [PATCH v10 09/13] dm-zone: use generic helpers to calculate offset from zone start Pankaj Raghav
2022-08-11 14:30 ` [PATCH v10 10/13] dm-table: allow zoned devices with non power-of-2 zone sizes Pankaj Raghav
2022-08-11 14:30 ` [PATCH v10 11/13] dm: call dm_zone_endio after the target endio callback for zoned devices Pankaj Raghav
2022-08-11 14:30 ` [PATCH v10 12/13] dm: introduce DM_EMULATED_ZONES target type Pankaj Raghav
2022-08-11 14:30 ` [PATCH v10 13/13] dm: add power-of-2 target for zoned devices with non power-of-2 zone sizes Pankaj Raghav
2022-08-11 16:15 ` Damien Le Moal
2022-08-12 7:25 ` Pankaj Raghav
2022-08-12 12:03 ` Joel Granados
2022-08-12 15:57 ` Damien Le Moal
2022-08-15 13:38 ` Pankaj Raghav [this message]
2022-08-15 18:56 ` Damien Le Moal
2022-08-16 8:02 ` Pankaj Raghav
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=b98ab80d-1bc0-a378-d438-09ef8b375836@samsung.com \
--to=p.raghav@samsung.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=damien.lemoal@wdc.com \
--cc=dm-devel@redhat.com \
--cc=gost.dev@samsung.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=j.granados@samsung.com \
--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=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