From: Christoph Hellwig <hch@lst.de>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>,
dm-devel@lists.linux.dev, Mike Snitzer <snitzer@redhat.com>,
linux-nvme@lists.infradead.org, Keith Busch <kbusch@kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v4 07/28] block: Introduce zone write plugging
Date: Tue, 2 Apr 2024 18:12:13 +0200 [thread overview]
Message-ID: <20240402161213.GB3527@lst.de> (raw)
In-Reply-To: <20240402123907.512027-8-dlemoal@kernel.org>
> + /* We can remove zone write plugs for zones that are empty or full. */
> + return !zwplug->wp_offset ||
> + zwplug->wp_offset >= disk->zone_capacity;
Nit: this condition easily fits onto a single line.
> +static inline struct blk_zone_wplug *
> +disk_lookup_zone_wplug(struct gendisk *disk, sector_t sector)
> +{
> + unsigned int zno = disk_zone_no(disk, sector);
> + unsigned int idx = hash_32(zno, disk->zone_wplugs_hash_bits);
> + struct blk_zone_wplug *zwplug;
> +
> + rcu_read_lock();
> + hlist_for_each_entry_rcu(zwplug, &disk->zone_wplugs_hash[idx], node) {
> + if (zwplug->zone_no == zno)
> + goto unlock;
> + }
> + zwplug = NULL;
> +
> +unlock:
> + rcu_read_unlock();
> + return zwplug;
> +}
Did we lose an atomic_inc_unless_zero here? This now just does a lookup
under RCU, but nothing to prevent the zwplug from beeing freed?
> + /* Resize the zone write plug memory pool if needed. */
> + if (disk->zone_wplugs_pool->min_nr != pool_size)
> + return mempool_resize(disk->zone_wplugs_pool, pool_size);
Note that a mempool_resize to the current size work just fine. It takes
a pointless lock, but given that this is something that doesn't happen
frequently that probably doesn't matter.
> +#include <linux/mempool.h>
> + mempool_t *zone_wplugs_pool;
Please use struct mempool_s here so that you only need a forward
declaration instead of pulling in another header.
next prev parent reply other threads:[~2024-04-02 16:12 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 12:38 [PATCH v4 00/28] Zone write plugging Damien Le Moal
2024-04-02 12:38 ` [PATCH v4 01/28] block: Restore sector of flush requests Damien Le Moal
2024-04-02 12:38 ` [PATCH v4 02/28] block: Remove req_bio_endio() Damien Le Moal
2024-04-02 18:02 ` Hannes Reinecke
2024-04-02 12:38 ` [PATCH v4 03/28] block: Introduce blk_zone_update_request_bio() Damien Le Moal
2024-04-02 12:38 ` [PATCH v4 04/28] block: Introduce bio_straddles_zones() and bio_offset_from_zone_start() Damien Le Moal
2024-04-02 12:38 ` [PATCH v4 05/28] block: Allow using bio_attempt_back_merge() internally Damien Le Moal
2024-04-02 12:38 ` [PATCH v4 06/28] block: Remember zone capacity when revalidating zones Damien Le Moal
2024-04-02 18:04 ` Hannes Reinecke
2024-04-02 12:38 ` [PATCH v4 07/28] block: Introduce zone write plugging Damien Le Moal
2024-04-02 16:12 ` Christoph Hellwig [this message]
2024-04-02 23:38 ` Damien Le Moal
2024-04-03 1:01 ` Jens Axboe
2024-04-03 1:02 ` Damien Le Moal
2024-04-02 18:26 ` Hannes Reinecke
2024-04-03 0:33 ` Damien Le Moal
2024-04-03 4:23 ` kernel test robot
2024-04-02 12:38 ` [PATCH v4 08/28] block: Fake max open zones limit when there is no limit Damien Le Moal
2024-04-02 12:38 ` [PATCH v4 09/28] block: Allow zero value of max_zone_append_sectors queue limit Damien Le Moal
2024-04-02 12:38 ` [PATCH v4 10/28] block: Implement zone append emulation Damien Le Moal
2024-04-02 12:38 ` [PATCH v4 11/28] block: Allow BIO-based drivers to use blk_revalidate_disk_zones() Damien Le Moal
2024-04-03 6:41 ` Hannes Reinecke
2024-04-02 12:38 ` [PATCH v4 12/28] dm: Use the block layer zone append emulation Damien Le Moal
2024-04-02 12:38 ` [PATCH v4 13/28] scsi: sd: " Damien Le Moal
2024-04-02 12:38 ` [PATCH v4 14/28] ublk_drv: Do not request ELEVATOR_F_ZBD_SEQ_WRITE elevator feature Damien Le Moal
2024-04-02 12:38 ` [PATCH v4 15/28] null_blk: " Damien Le Moal
2024-04-02 12:38 ` [PATCH v4 16/28] null_blk: Introduce zone_append_max_sectors attribute Damien Le Moal
2024-04-02 12:38 ` [PATCH v4 17/28] null_blk: Introduce fua attribute Damien Le Moal
2024-04-03 3:56 ` Chaitanya Kulkarni
2024-04-03 3:58 ` Damien Le Moal
2024-04-03 4:43 ` Christoph Hellwig
2024-04-02 12:38 ` [PATCH v4 18/28] nvmet: zns: Do not reference the gendisk conv_zones_bitmap Damien Le Moal
2024-04-02 12:38 ` [PATCH v4 19/28] block: Remove BLK_STS_ZONE_RESOURCE Damien Le Moal
2024-04-02 12:38 ` [PATCH v4 20/28] block: Simplify blk_revalidate_disk_zones() interface Damien Le Moal
2024-04-02 12:39 ` [PATCH v4 21/28] block: mq-deadline: Remove support for zone write locking Damien Le Moal
2024-04-02 12:39 ` [PATCH v4 22/28] block: Remove elevator required features Damien Le Moal
2024-04-02 12:39 ` [PATCH v4 23/28] block: Do not check zone type in blk_check_zone_append() Damien Le Moal
2024-04-02 12:39 ` [PATCH v4 24/28] block: Move zone related debugfs attribute to blk-zoned.c Damien Le Moal
2024-04-02 12:39 ` [PATCH v4 25/28] block: Replace zone_wlock debugfs entry with zone_wplugs entry Damien Le Moal
2024-04-03 6:43 ` Hannes Reinecke
2024-04-02 12:39 ` [PATCH v4 26/28] block: Remove zone write locking Damien Le Moal
2024-04-02 16:03 ` Christoph Hellwig
2024-04-03 6:43 ` Hannes Reinecke
2024-04-02 12:39 ` [PATCH v4 27/28] block: Do not force select mq-deadline with CONFIG_BLK_DEV_ZONED Damien Le Moal
2024-04-02 12:39 ` [PATCH v4 28/28] block: Do not special-case plugging of zone write operations Damien Le Moal
2024-04-03 8:15 ` [PATCH v4 00/28] Zone write plugging Hans Holmberg
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=20240402161213.GB3527@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=dm-devel@lists.linux.dev \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--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