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 04/12] bcache: bch_nvmpg_alloc_pages() of the buddy
Date: Sun, 12 Dec 2021 13:14:31 -0700 [thread overview]
Message-ID: <22d13a6d-4ac7-18e5-13cd-84e6353755be@kernel.dk> (raw)
In-Reply-To: <20211212170552.2812-5-colyli@suse.de>
On 12/12/21 10:05 AM, Coly Li wrote:
> +/* If not found, it will create if create == true */
> +static struct bch_nvmpg_head *find_nvmpg_head(const char *uuid, bool create)
> +{
> + struct bch_nvmpg_set_header *set_header = global_nvmpg_set->set_header;
> + struct bch_nvmpg_head *head = NULL;
> + int i;
> +
> + if (set_header == NULL)
> + goto out;
> +
> + for (i = 0; i < set_header->size; i++) {
> + struct bch_nvmpg_head *h = &set_header->heads[i];
> +
> + if (h->state != BCH_NVMPG_HD_STAT_ALLOC)
> + continue;
> +
> + if (!memcmp(uuid, h->uuid, 16)) {
> + head = h;
> + break;
> + }
> + }
> +
> + if (!head && create) {
> + u32 used = set_header->used;
> +
> + if (set_header->size > used) {
> + head = &set_header->heads[used];
> + memset(head, 0, sizeof(struct bch_nvmpg_head));
> + head->state = BCH_NVMPG_HD_STAT_ALLOC;
> + memcpy(head->uuid, uuid, 16);
> + global_nvmpg_set->heads_used++;
> + set_header->used++;
> + } else
> + pr_info("No free bch_nvmpg_head\n");
> + }
Use {} consistently. Again probably just some printk that should go
away.
> +static struct bch_nvmpg_recs *find_nvmpg_recs(struct bch_nvmpg_ns *ns,
> + struct bch_nvmpg_head *head,
> + bool create)
> +{
> + int ns_id = ns->sb->this_ns;
> + struct bch_nvmpg_recs *prev_recs = NULL, *recs = NULL;
> +
> + recs = bch_nvmpg_offset_to_ptr(head->recs_offset[ns_id]);
> +
> + /* If create=false, we return recs[nr] */
> + if (!create)
> + return recs;
Would this be cleaner to handle in the caller?
> +static void add_nvmpg_rec(struct bch_nvmpg_ns *ns,
> + struct bch_nvmpg_recs *recs,
> + unsigned long nvmpg_offset,
> + int order)
> +{
> + int i, ns_id;
> + unsigned long pgoff;
> +
> + pgoff = bch_nvmpg_offset_to_pgoff(nvmpg_offset);
> + ns_id = ns->sb->this_ns;
> +
> + for (i = 0; i < recs->size; i++) {
> + if (recs->recs[i].pgoff == 0) {
> + recs->recs[i].pgoff = pgoff;
> + recs->recs[i].order = order;
> + recs->recs[i].ns_id = ns_id;
> + recs->used++;
> + break;
> + }
> + }
> + BUG_ON(i == recs->size);
No BUG_ON's, please. It only truly belongs in core code for cases where
error handling isn't possible, does not apply here.
> diff --git a/drivers/md/bcache/nvmpg.h b/drivers/md/bcache/nvmpg.h
> index 55778d4db7da..d03f3241b45a 100644
> --- a/drivers/md/bcache/nvmpg.h
> +++ b/drivers/md/bcache/nvmpg.h
> @@ -76,6 +76,9 @@ struct bch_nvmpg_set {
> /* Indicate which field in bch_nvmpg_sb to be updated */
> #define BCH_NVMPG_TOTAL_NS 0 /* total_ns */
>
> +#define BCH_PGOFF_TO_KVADDR(pgoff) \
> + ((void *)((unsigned long)(pgoff) << PAGE_SHIFT))
Pretty sure we have a general kernel helper for this, better to use that
rather than duplicate it.
--
Jens Axboe
next prev parent reply other threads:[~2021-12-12 20:15 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 [this message]
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
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=22d13a6d-4ac7-18e5-13cd-84e6353755be@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