From: Ryan Roberts <ryan.roberts@arm.com>
To: Uladzislau Rezki <urezki@gmail.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Vishal Moola <vishal.moola@gmail.com>,
Dev Jain <dev.jain@arm.com>, Baoquan He <bhe@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] mm/vmalloc: Add attempt_larger_order_alloc parameter
Date: Thu, 18 Dec 2025 11:14:55 +0000 [thread overview]
Message-ID: <026b42f6-2f83-448a-9b45-cc8740dd8d50@arm.com> (raw)
In-Reply-To: <aUMNyfeoEh_tJHpT@pc636>
On 17/12/2025 20:08, Uladzislau Rezki wrote:
>>
>> What do you think?
>>
> I think with such big improvement we do not need a configuration knob.
> Your change will fully complete Vishal's work, i.e an idea to allocate
> using high-order pages.
Yes agreed. How do you want to proceed? I'll tidy up my patch and post it
properly if you like? (likely won't be until Tuesday though). Or if you prefer
to work on it, that's fine by me too.
Personally I think we should aim to get the fix into 6.19 to avoid the
performance regression (even if we think the allocation pattern of those
benchmarks is not the common case).
Thanks,
Ryan
>
> --
> Uladzislau Rezki
next prev parent reply other threads:[~2025-12-18 11:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 21:19 [PATCH 1/2] mm/vmalloc: Add large-order allocation helper Uladzislau Rezki (Sony)
2025-12-16 21:19 ` [PATCH 2/2] mm/vmalloc: Add attempt_larger_order_alloc parameter Uladzislau Rezki (Sony)
2025-12-16 23:36 ` Andrew Morton
2025-12-17 11:37 ` Uladzislau Rezki
2025-12-17 3:54 ` Baoquan He
2025-12-17 11:44 ` Uladzislau Rezki
2025-12-17 11:49 ` Dev Jain
2025-12-17 11:53 ` Uladzislau Rezki
2025-12-18 10:34 ` Baoquan He
2025-12-17 8:27 ` Ryan Roberts
2025-12-17 12:02 ` Uladzislau Rezki
2025-12-17 15:20 ` Ryan Roberts
2025-12-17 17:01 ` Ryan Roberts
2025-12-17 19:22 ` Uladzislau Rezki
2025-12-18 11:12 ` Ryan Roberts
2025-12-18 11:33 ` Uladzislau Rezki
2025-12-17 20:08 ` Uladzislau Rezki
2025-12-18 11:14 ` Ryan Roberts [this message]
2025-12-18 11:29 ` Uladzislau Rezki
2025-12-18 4:55 ` Dev Jain
2025-12-18 11:53 ` Ryan Roberts
2025-12-18 11:56 ` Ryan Roberts
2025-12-19 8:33 ` David Hildenbrand (Red Hat)
2025-12-19 11:17 ` Ryan Roberts
2025-12-19 0:34 ` Vishal Moola (Oracle)
2025-12-19 11:23 ` Ryan Roberts
2025-12-24 6:35 ` Dev Jain
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=026b42f6-2f83-448a-9b45-cc8740dd8d50@arm.com \
--to=ryan.roberts@arm.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dev.jain@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=urezki@gmail.com \
--cc=vishal.moola@gmail.com \
/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