linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Rientjes <rientjes@google.com>,
	Christoph Lameter <cl@linux.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Roman Gushchin <roman.gushchin@linux.dev>,
	Hyeonggon Yoo <42.hyeyoo@gmail.com>
Subject: [GIT PULL] slab updates for 6.16
Date: Wed, 4 Jun 2025 11:02:26 +0200	[thread overview]
Message-ID: <7f9a7fe2-da23-422f-a5f1-14fa99eb38d9@suse.cz> (raw)

Hi Linus,

please pull the latest slab updates from:

  git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git tags/slab-for-6.16

AFAIK no conflicts. A small PR this time, but the next merge window should
be different. The second commit came somewhat late hence the PR is also
later than usual to allow for more -next soak time.

Thanks,
Vlastimil

======================================

* Make kvmalloc() more suitable for callers that need it to succeed, but
  without unnecessary overhead by reclaim and compaction to get a physically
  contiguous allocation. Instead fallback to vmalloc() more easily by default,
  unless instructed by __GFP_RETRY_MAYFAIL to prefer kmalloc() harder.
  This should allow the removal of a xfs-specific workaround (Michal Hocko)

* Remove potentially excessive warnings due to memory pressure when allocating
  structures for per-object allocation profiling metadata (Usama Arif)

----------------------------------------------------------------
Michal Hocko (1):
      mm: kvmalloc: make kmalloc fast path real fast path

Usama Arif (1):
      mm: slub: only warn once when allocating slab obj extensions fails

 mm/slub.c | 15 +++++++++------
 1 file changed, 9 insertions(+), 6 deletions(-)


             reply	other threads:[~2025-06-04  9:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-04  9:02 Vlastimil Babka [this message]
2025-06-04 16:37 ` 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=7f9a7fe2-da23-422f-a5f1-14fa99eb38d9@suse.cz \
    --to=vbabka@suse.cz \
    --cc=42.hyeyoo@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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