From: Johannes Thumshirn <jthumshirn@suse.de>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
linux-mm@kvack.org, Jens Axboe <axboe@kernel.dk>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH 01/10] mempool: Add mempool_init()/mempool_exit()
Date: Wed, 9 May 2018 09:54:07 +0200 [thread overview]
Message-ID: <20180509075407.oz7l6gkolepciudx@linux-x5ow.site> (raw)
In-Reply-To: <20180509013358.16399-2-kent.overstreet@gmail.com>
On Tue, May 08, 2018 at 09:33:49PM -0400, Kent Overstreet wrote:
> +/**
> + * mempool_destroy - exit a mempool initialized with mempool_init()
^ mempool_exit()
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nurnberg
GF: Felix Imendorffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nurnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2018-05-09 7:54 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 1:33 [PATCH 00/10] Misc block layer patches for bcachefs Kent Overstreet
2018-05-09 1:33 ` [PATCH 01/10] mempool: Add mempool_init()/mempool_exit() Kent Overstreet
2018-05-09 7:54 ` Johannes Thumshirn [this message]
2018-05-11 21:11 ` Jens Axboe
2018-05-14 19:11 ` Kent Overstreet
2018-05-09 1:33 ` [PATCH 02/10] block: Convert bio_set to mempool_init() Kent Overstreet
2018-05-18 16:20 ` Christoph Hellwig
2018-05-18 16:21 ` Christoph Hellwig
2018-05-18 17:36 ` Kent Overstreet
2018-05-09 1:33 ` [PATCH 03/10] block: Add bioset_init()/bioset_exit() Kent Overstreet
2018-05-09 1:33 ` [PATCH 04/10] block: Use bioset_init() for fs_bio_set Kent Overstreet
2018-05-09 1:33 ` [PATCH 05/10] block: Add bio_copy_data_iter(), zero_fill_bio_iter() Kent Overstreet
2018-05-09 1:33 ` [PATCH 06/10] block: Split out bio_list_copy_data() Kent Overstreet
2018-05-09 1:33 ` [PATCH 07/10] block: Add missing flush_dcache_page() call Kent Overstreet
2018-05-09 1:33 ` [PATCH 08/10] block: Add warning for bi_next not NULL in bio_endio() Kent Overstreet
2018-05-09 1:33 ` [PATCH 09/10] block: Export bio check/set pages_dirty Kent Overstreet
2018-05-09 1:33 ` [PATCH 10/10] block: Add sysfs entry for fua support Kent Overstreet
2018-05-11 21:13 ` [PATCH 00/10] Misc block layer patches for bcachefs Jens Axboe
2018-05-18 16:23 ` Christoph Hellwig
2018-05-18 16:33 ` Jens Axboe
2018-05-14 19:24 ` Jens Axboe
2018-05-14 19:24 ` Kent Overstreet
2018-05-17 20:54 ` Bart Van Assche
2018-05-18 9:06 ` Kent Overstreet
2018-05-18 15:12 ` Bart Van Assche
2018-05-20 22:17 ` Kent Overstreet
2018-05-20 22:19 ` Bart Van Assche
2018-05-20 22:31 ` Kent Overstreet
2018-05-20 22:35 ` Bart Van Assche
2018-05-20 23:00 ` Kent Overstreet
2018-05-20 23:10 ` Bart Van Assche
2018-05-20 23:21 ` Kent Overstreet
2018-05-20 23:40 ` Bart Van Assche
2018-05-20 23:58 ` Kent Overstreet
2018-05-21 15:11 ` Bart Van Assche
2018-05-21 18:37 ` Omar Sandoval
2018-05-21 18:46 ` Bart Van Assche
2018-05-22 22:01 ` Bart Van Assche
[not found] <20180518074918.13816-1-kent.overstreet@gmail.com>
2018-05-18 7:48 ` [PATCH 01/10] mempool: Add mempool_init()/mempool_exit() Kent Overstreet
2018-05-18 8:21 ` Johannes Thumshirn
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=20180509075407.oz7l6gkolepciudx@linux-x5ow.site \
--to=jthumshirn@suse.de \
--cc=axboe@kernel.dk \
--cc=kent.overstreet@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@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