From: Christoph Lameter <cl@gentwo.de>
To: Feng Tang <feng.tang@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Vlastimil Babka <vbabka@suse.cz>,
Roman Gushchin <roman.gushchin@linux.dev>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
dave.hansen@intel.com, Robin Murphy <robin.murphy@arm.com>,
John Garry <john.garry@huawei.com>
Subject: Re: [PATCH v1] mm/slub: enable debugging memory wasting of kmalloc
Date: Fri, 1 Jul 2022 16:37:00 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2207011635040.588600@gentwo.de> (raw)
In-Reply-To: <20220701135954.45045-1-feng.tang@intel.com>
On Fri, 1 Jul 2022, Feng Tang wrote:
> static void *__slab_alloc(struct kmem_cache *s, gfp_t gfpflags, int node,
> - unsigned long addr, struct kmem_cache_cpu *c)
> + unsigned long addr, struct kmem_cache_cpu *c, unsigned int orig_size)
> {
It would be good to avoid expanding the basic slab handling functions for
kmalloc. Can we restrict the mods to the kmalloc related functions?
next prev parent reply other threads:[~2022-07-01 14:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 13:59 Feng Tang
2022-07-01 14:37 ` Christoph Lameter [this message]
2022-07-01 15:04 ` Feng Tang
2022-07-03 14:17 ` Hyeonggon Yoo
2022-07-04 5:56 ` Feng Tang
2022-07-04 10:05 ` Hyeonggon Yoo
2022-07-05 2:34 ` Feng Tang
2022-07-11 8:15 ` Vlastimil Babka
2022-07-11 11:54 ` Feng Tang
2022-07-13 7:36 ` Feng Tang
2022-07-14 20:11 ` Vlastimil Babka
2022-07-15 8:29 ` Feng Tang
2022-07-19 13:45 ` Feng Tang
2022-07-19 14:39 ` Vlastimil Babka
2022-07-19 15:03 ` Feng Tang
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=alpine.DEB.2.22.394.2207011635040.588600@gentwo.de \
--to=cl@gentwo.de \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=feng.tang@intel.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=robin.murphy@arm.com \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@suse.cz \
/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