From: Vlastimil Babka <vbabka@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
patches@lists.linux.dev,
Roman Gushchin <roman.gushchin@linux.dev>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>
Subject: [GIT PULL] slab for 5.20/6.0
Date: Mon, 1 Aug 2022 12:29:48 +0200 [thread overview]
Message-ID: <9a5df89d-e27a-22b4-faae-be65f6c7f54d@suse.cz> (raw)
Linus,
please pull the latest slab changes from
git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git tags/slab-for-5.20_or_6.0
======================================
- An addition of 'accounted' flag to slab allocation tracepoints to indicate
memcg_kmem accounting, by Vasily.
- An optimization of memcg handling in freeing paths, by Muchun.
- Various smaller fixes and cleanups.
Thanks,
Vlastimil
----------------------------------------------------------------
Hyeonggon Yoo (2):
mm/sl[au]b: use own bulk free function when bulk alloc failed
mm/slab_common: move generic bulk alloc/free functions to SLOB
Jiapeng Chong (1):
mm, slab: fix bad alignments
Muchun Song (1):
mm: slab: optimize memcg_slab_free_hook()
Stéphane Graber (1):
tools/vm/slabinfo: Handle files in debugfs
Vasily Averin (1):
mm/tracing: add 'accounted' entry into output of allocation tracepoints
Xiongwei Song (1):
mm/slub: Simplify __kmem_cache_alias()
include/trace/events/kmem.h | 40 +++++++++++-------
mm/slab.c | 20 ++++-----
mm/slab.h | 39 ++++--------------
mm/slab_common.c | 36 ++---------------
mm/slob.c | 33 +++++++++++----
mm/slub.c | 98 +++++++++++++++++----------------------------
tools/vm/slabinfo.c | 26 +++++++++++-
7 files changed, 134 insertions(+), 158 deletions(-)
next reply other threads:[~2022-08-01 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 10:29 Vlastimil Babka [this message]
2022-08-01 19:55 ` pr-tracker-bot
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=9a5df89d-e27a-22b4-faae-be65f6c7f54d@suse.cz \
--to=vbabka@suse.cz \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=patches@lists.linux.dev \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=torvalds@linux-foundation.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