From: Kent Overstreet <kent.overstreet@linux.dev>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] mempool: kvmalloc pool
Date: Fri, 2 Feb 2024 04:44:49 -0500 [thread overview]
Message-ID: <75rltarf5vipizh4pvqdqpx3nxhxle7whc3wzfrbdppt5mdxlk@bhjeqctzqom6> (raw)
In-Reply-To: <20240202003904.621992e356bc23f1a122dba3@linux-foundation.org>
On Fri, Feb 02, 2024 at 12:39:04AM -0800, Andrew Morton wrote:
> On Thu, 1 Feb 2024 07:15:44 -0500 Kent Overstreet <kent.overstreet@linux.dev> wrote:
>
> > Add mempool_init_kvmalloc_pool() and mempool_create_kvmalloc_pool(),
> > which wrap kvmalloc() instead of kmalloc() - kmalloc() with a vmalloc()
> > fallback.
> >
>
> Why do we need this?
>
> Can we expect to see users of this?
Yeah, I should have had that in the commit message - it's replacing
mempool_init_kvpmalloc_pool() in fs/bcachefs/util.c
prev parent reply other threads:[~2024-02-02 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 12:15 [PATCH] mempool: kvmalloc pool Kent Overstreet
2024-02-02 8:39 ` Andrew Morton
2024-02-02 9:44 ` Kent Overstreet [this message]
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=75rltarf5vipizh4pvqdqpx3nxhxle7whc3wzfrbdppt5mdxlk@bhjeqctzqom6 \
--to=kent.overstreet@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).