From: NeilBrown <neilb@suse.com>
To: Christoph Hellwig <hch@lst.de>, shli@fb.com
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH 2/2] raid5-cache: use a mempool for the metadata block
Date: Wed, 09 Dec 2015 10:27:25 +1100 [thread overview]
Message-ID: <878u54r06a.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <1449072638-15409-3-git-send-email-hch@lst.de>
[-- Attachment #1: Type: text/plain, Size: 992 bytes --]
On Thu, Dec 03 2015, Christoph Hellwig wrote:
> +
> error:
> md_unregister_thread(&log->reclaim_thread);
> reclaim_thread:
> + mempool_destroy(log->meta_pool);
> +out_mempool:
> bioset_free(log->bs);
> io_bs:
These cascading goto labels always bother me.
As mempool_destroy accepts NULL, we don't need "out_mempool", we can
just "goto reclaim_thread", or even "goto error" as md_unregsiter_thread
copes with NULL too.
If we use:
if (log->bs)
bioset_free(log->bs);
or modified bioset_free, we could just have a single 'error' label...
But that is just cosmetic. I like the patch once we agree on value for
R5L_POOL_SIZE.
Thanks,
NeilBrown
> kmem_cache_destroy(log->io_kc);
> @@ -1192,6 +1201,7 @@ io_kc:
> void r5l_exit_log(struct r5l_log *log)
> {
> md_unregister_thread(&log->reclaim_thread);
> + mempool_destroy(log->meta_pool);
> bioset_free(log->bs);
> kmem_cache_destroy(log->io_kc);
> kfree(log);
> --
> 1.9.1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2015-12-08 23:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 16:10 [RFC] using mempools for raid5-cache Christoph Hellwig
2015-12-02 16:10 ` [PATCH 1/2] raid5-cache: use a bio_set Christoph Hellwig
2015-12-03 5:01 ` Shaohua Li
2015-12-08 23:22 ` NeilBrown
2015-12-14 21:12 ` Christoph Hellwig
2015-12-02 16:10 ` [PATCH 2/2] raid5-cache: use a mempool for the metadata block Christoph Hellwig
2015-12-08 23:27 ` NeilBrown [this message]
2015-12-03 4:49 ` [RFC] using mempools for raid5-cache Shaohua Li
2015-12-09 0:36 ` NeilBrown
2015-12-09 1:28 ` Shaohua Li
2015-12-09 6:34 ` NeilBrown
2015-12-10 23:40 ` Shaohua Li
2015-12-11 0:09 ` NeilBrown
2015-12-11 1:10 ` Shaohua Li
2015-12-11 1:56 ` NeilBrown
2015-12-09 13:51 ` Wols Lists
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=878u54r06a.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=hch@lst.de \
--cc=linux-raid@vger.kernel.org \
--cc=shli@fb.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).