From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: Swaraj Gaikwad <swarajgaikwad1925@gmail.com>
Cc: akpm@linux-foundation.org, david.hunter.linux@gmail.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
osalvador@suse.de, skhan@linuxfoundation.org
Subject: Re: [PATCH] mm/memory_hotplug: Cache auto_movable stats to optimize online check
Date: Thu, 18 Dec 2025 09:54:36 +0100 [thread overview]
Message-ID: <b5c3c6ba-ae4a-488b-be37-bbb612bb414e@kernel.org> (raw)
In-Reply-To: <20251218064159.7230-1-swarajgaikwad1925@gmail.com>
On 12/18/25 07:41, Swaraj Gaikwad wrote:
> Hi David,
Hi!
>
> I’m just checking in on this patch to see if you’ve had a chance to review
> the benchmark results I shared last week.
Not really, still traveling and this is veeeery low priority :)
> To recap, the caching reduced the
> execution time for the NUMA_NO_NODE case from ~2402 ns to ~453 ns in my test
> environment.
Yeah, but these micro-benchmarks don't really matter ... at all. What
would be interesting is what happens when you hotplug a lot of memory to
a system with a lot of nodes. I suspect it won't really be a problem.
>
> Please let me know if the performance gain justifies the change in your view,or
> if you would prefer I send a v2 that simply updates the TODO comment as you suggested.
I'd prefer if things that are not a real problem would not consume my
bandwidth while traveling ;)
Anyhow, there was a kernel bot complaint that you are using "struct
auto_movable_stats" before the compiler knows about it (and its size).
When you resend, make sure to better describe the "why" we are doing it.
It cleans up the code a little, so that could be used as an argument.
--
Cheers
David
prev parent reply other threads:[~2025-12-18 8:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-06 21:25 Swaraj Gaikwad
2025-12-07 10:16 ` kernel test robot
2025-12-07 13:30 ` David Hildenbrand (Red Hat)
2025-12-07 23:10 ` Swaraj Gaikwad
2025-12-18 6:41 ` Swaraj Gaikwad
2025-12-18 8:54 ` David Hildenbrand (Red Hat) [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=b5c3c6ba-ae4a-488b-be37-bbb612bb414e@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david.hunter.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=skhan@linuxfoundation.org \
--cc=swarajgaikwad1925@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