From: Matthew Wilcox <willy@infradead.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: linux-mm@kvack.org, Harry Yoo <harry.yoo@oracle.com>,
David Rientjes <rientjes@google.com>,
Christoph Lameter <cl@linux.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH RFC] mm, slab: warn when increasing refcount on large kmalloc page
Date: Wed, 23 Apr 2025 19:20:04 +0100 [thread overview]
Message-ID: <aAkvVMxZJAEq9ooW@casper.infradead.org> (raw)
In-Reply-To: <20250417074102.4543-2-vbabka@suse.cz>
On Thu, Apr 17, 2025 at 09:41:03AM +0200, Vlastimil Babka wrote:
> I'd like to expose this via slab-next and see if there are any reports.
> If not for few weeks, maybe proceed immediately to freezing refcount and
> handling it in get_page/put_page exactly like folio_test_slab. Thoughts?
I think you're being too cautious ;-) I had a bit of a play around to
see if there's a way of getting gcc to optimise the generated code for
this, but didn't come up with anything too clever.
prev parent reply other threads:[~2025-04-23 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 7:41 Vlastimil Babka
2025-04-18 14:04 ` Harry Yoo
2025-04-20 2:41 ` David Rientjes
2025-04-20 2:46 ` David Rientjes
2025-04-23 18:20 ` Matthew Wilcox [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=aAkvVMxZJAEq9ooW@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=harry.yoo@oracle.com \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--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