From: Jens Axboe <axboe@kernel.dk>
To: Coly Li <colyli@suse.de>
Cc: linux-bcache@vger.kernel.org, linux-block@vger.kernel.org,
Jianpeng Ma <jianpeng.ma@intel.com>,
Qiaowei Ren <qiaowei.ren@intel.com>,
Christoph Hellwig <hch@lst.de>,
Dan Williams <dan.j.williams@intel.com>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH v13 05/12] bcache: bch_nvmpg_free_pages() of the buddy allocator
Date: Sun, 12 Dec 2021 13:16:48 -0700 [thread overview]
Message-ID: <34997a50-52c0-33b8-a3ff-e0c02389f365@kernel.dk> (raw)
In-Reply-To: <20211212170552.2812-6-colyli@suse.de>
On 12/12/21 10:05 AM, Coly Li wrote:
> diff --git a/drivers/md/bcache/nvmpg.c b/drivers/md/bcache/nvmpg.c
> index a920779eb548..8ce0c4389b42 100644
> --- a/drivers/md/bcache/nvmpg.c
> +++ b/drivers/md/bcache/nvmpg.c
> @@ -248,6 +248,57 @@ static int init_nvmpg_set_header(struct bch_nvmpg_ns *ns)
> return rc;
> }
>
> +static void __free_space(struct bch_nvmpg_ns *ns, unsigned long nvmpg_offset,
> + int order)
> +{
> + unsigned long add_pages = (1L << order);
> + pgoff_t pgoff;
> + struct page *page;
> + void *va;
> +
> + if (nvmpg_offset == 0) {
> + pr_err("free pages on offset 0\n");
> + return;
> + }
> +
> + page = bch_nvmpg_va_to_pg(bch_nvmpg_offset_to_ptr(nvmpg_offset));
> + WARN_ON((!page) || (page->private != order));
> + pgoff = page->index;
> +
> + while (order < BCH_MAX_ORDER - 1) {
> + struct page *buddy_page;
> +
> + pgoff_t buddy_pgoff = pgoff ^ (1L << order);
> + pgoff_t parent_pgoff = pgoff & ~(1L << order);
> +
> + if ((parent_pgoff + (1L << (order + 1)) > ns->pages_total))
> + break;
> +
> + va = bch_nvmpg_pgoff_to_ptr(ns, buddy_pgoff);
> + buddy_page = bch_nvmpg_va_to_pg(va);
> + WARN_ON(!buddy_page);
> +
> + if (PageBuddy(buddy_page) && (buddy_page->private == order)) {
> + list_del((struct list_head *)&buddy_page->zone_device_data);
> + __ClearPageBuddy(buddy_page);
> + pgoff = parent_pgoff;
> + order++;
> + continue;
> + }
> + break;
> + }
> +
> + va = bch_nvmpg_pgoff_to_ptr(ns, pgoff);
> + page = bch_nvmpg_va_to_pg(va);
> + WARN_ON(!page);
> + list_add((struct list_head *)&page->zone_device_data,
> + &ns->free_area[order]);
> + page->index = pgoff;
> + set_page_private(page, order);
> + __SetPageBuddy(page);
> + ns->free += add_pages;
> +}
There are 3 WARN_ON's in here. If you absolutely must use a WARN_ON,
then make them WARN_ON_ONCE(). Ditto in other spots in this patch.
> +void bch_nvmpg_free_pages(unsigned long nvmpg_offset, int order,
> + const char *uuid)
> +{
> + struct bch_nvmpg_ns *ns;
> + struct bch_nvmpg_head *head;
> + struct bch_nvmpg_recs *recs;
> + int r;
> +
> + mutex_lock(&global_nvmpg_set->lock);
> +
> + ns = global_nvmpg_set->ns_tbl[BCH_NVMPG_GET_NS_ID(nvmpg_offset)];
> + if (!ns) {
> + pr_err("can't find namespace by given kaddr from namespace\n");
> + goto unlock;
> + }
> +
> + head = find_nvmpg_head(uuid, false);
> + if (!head) {
> + pr_err("can't found bch_nvmpg_head by uuid\n");
> + goto unlock;
> + }
> +
> + recs = find_nvmpg_recs(ns, head, false);
> + if (!recs) {
> + pr_err("can't find bch_nvmpg_recs by uuid\n");
> + goto unlock;
> + }
> +
> + r = remove_nvmpg_rec(recs, ns->sb->this_ns, nvmpg_offset, order);
> + if (r < 0) {
> + pr_err("can't find bch_nvmpg_rec\n");
> + goto unlock;
> + }
> +
> + __free_space(ns, nvmpg_offset, order);
> +
> +unlock:
> + mutex_unlock(&global_nvmpg_set->lock);
> +}
Again tons of useless error prints. Make them return a proper error
instad of just making things void...
> @@ -686,6 +835,7 @@ struct bch_nvmpg_ns *bch_register_namespace(const char *dev_path)
> ns->pages_offset = sb->pages_offset;
> ns->pages_total = sb->pages_total;
> ns->sb = sb;
> + /* increase by __free_space() */
> ns->free = 0;
> ns->bdev = bdev;
> ns->set = global_nvmpg_set;
Does that hunk belong in here?
--
Jens Axboe
next prev parent reply other threads:[~2021-12-12 20:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 17:05 [PATCH v13 00/12] bcache for 5.17: enable NVDIMM for bcache journal Coly Li
2021-12-12 17:05 ` [PATCH v13 01/12] bcache: add initial data structures for nvm pages Coly Li
2021-12-12 17:05 ` [PATCH v13 02/12] bcache: initialize the nvm pages allocator Coly Li
2021-12-12 19:34 ` Jens Axboe
2021-12-28 5:29 ` Coly Li
2021-12-12 17:05 ` [PATCH v13 03/12] bcache: initialization of the buddy Coly Li
2021-12-12 20:10 ` Jens Axboe
2021-12-28 5:29 ` Coly Li
2021-12-15 16:20 ` Dan Carpenter
2021-12-28 5:12 ` Coly Li
2021-12-12 17:05 ` [PATCH v13 04/12] bcache: bch_nvmpg_alloc_pages() " Coly Li
2021-12-12 20:14 ` Jens Axboe
2021-12-28 5:29 ` Coly Li
2021-12-12 17:05 ` [PATCH v13 05/12] bcache: bch_nvmpg_free_pages() of the buddy allocator Coly Li
2021-12-12 20:16 ` Jens Axboe [this message]
2021-12-28 5:29 ` Coly Li
2022-02-21 12:36 ` yukuai (C)
2022-02-22 5:03 ` Ma, Jianpeng
2021-12-12 17:05 ` [PATCH v13 06/12] bcache: get recs list head for allocated pages by specific uuid Coly Li
2021-12-12 20:18 ` Jens Axboe
2021-12-12 17:05 ` [PATCH v13 07/12] bcache: use bucket index to set GC_MARK_METADATA for journal buckets in bch_btree_gc_finish() Coly Li
2021-12-12 17:05 ` [PATCH v13 08/12] bcache: add BCH_FEATURE_INCOMPAT_NVDIMM_META into incompat feature set Coly Li
2021-12-12 17:05 ` [PATCH v13 09/12] bcache: initialize bcache journal for NVDIMM meta device Coly Li
2021-12-12 17:05 ` [PATCH v13 10/12] bcache: support storing bcache journal into " Coly Li
2021-12-12 17:05 ` [PATCH v13 11/12] bcache: read jset from NVDIMM pages for journal replay Coly Li
2021-12-12 17:05 ` [PATCH v13 12/12] bcache: add sysfs interface register_nvdimm_meta to register NVDIMM meta device Coly Li
2021-12-12 20:20 ` [PATCH v13 00/12] bcache for 5.17: enable NVDIMM for bcache journal Jens Axboe
2021-12-28 5:29 ` Coly Li
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=34997a50-52c0-33b8-a3ff-e0c02389f365@kernel.dk \
--to=axboe@kernel.dk \
--cc=colyli@suse.de \
--cc=dan.j.williams@intel.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jianpeng.ma@intel.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=qiaowei.ren@intel.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).