From: Mike Snitzer <snitzer@redhat.com>
To: David Rientjes <rientjes@google.com>
Cc: Alasdair Kergon <agk@redhat.com>, Neil Brown <neilb@suse.de>,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
dm-devel@redhat.com
Subject: Re: dm log userspace: use mempool_create_kmalloc_pool()
Date: Wed, 11 Mar 2015 08:58:52 -0400 [thread overview]
Message-ID: <20150311125852.GA28768@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1503071642540.2772@chino.kir.corp.google.com>
On Sat, Mar 07 2015 at 7:43pm -0500,
David Rientjes <rientjes@google.com> wrote:
> Mempools created for kmalloc caches should use
> mempool_create_kmalloc_pool().
>
> Cc: Alasdair Kergon <agk@redhat.com>
> Cc: Mike Snitzer <snitzer@redhat.com>
> Cc: Neil Brown <neilb@suse.de>
> Signed-off-by: David Rientjes <rientjes@google.com>
Thanks David, I'll get this queued up.
next prev parent reply other threads:[~2015-03-11 12:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 0:43 [patch] dm log userspace: use mempool_create_kmalloc_pool() David Rientjes
2015-03-11 12:58 ` Mike Snitzer [this message]
2015-03-18 22:30 ` Mike Snitzer
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=20150311125852.GA28768@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=rientjes@google.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).