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>,
Feng Tang <feng.tang@intel.com>,
Jay Patel <jaypatel@linux.ibm.com>
Subject: [GIT PULL] slab updates for 6.7
Date: Fri, 27 Oct 2023 16:38:19 +0200 [thread overview]
Message-ID: <7f4cd48e-492c-24f7-6fef-e3b50eace6ba@suse.cz> (raw)
Hi Linus,
once the merge window opens, please pull the latest slab updates from:
git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git tags/slab-for-6.7
Thanks,
Vlastimil
======================================
* SLUB: slab order calculation refactoring (Vlastimil Babka, Feng Tang)
Recent proposals to tune the slab order calculations have prompted us to
look at the current code and refactor it to make it easier to follow and
eliminate some odd corner cases. The refactoring is mostly non-functional
changes, but should make the actual tuning easier to implement and review.
----------------------------------------------------------------
Feng Tang (1):
mm/slub: add sanity check for slub_min/max_order cmdline setup
Vlastimil Babka (4):
mm/slub: simplify the last resort slab order calculation
mm/slub: remove min_objects loop from calculate_order()
mm/slub: attempt to find layouts up to 1/2 waste in calculate_order()
mm/slub: refactor calculate_order() and calc_slab_order()
mm/slub.c | 73 +++++++++++++++++++++++++++++++--------------------------------
1 file changed, 36 insertions(+), 37 deletions(-)
next reply other threads:[~2023-10-27 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 14:38 Vlastimil Babka [this message]
2023-10-31 5:42 ` [GIT PULL] slab updates for 6.7 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=7f4cd48e-492c-24f7-6fef-e3b50eace6ba@suse.cz \
--to=vbabka@suse.cz \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=feng.tang@intel.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=jaypatel@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.