From: Johannes Weiner <hannes@cmpxchg.org>
To: Damian Dudycz <damiandudycz@yahoo.com>
Cc: linux-mm@kvack.org, sam@gentoo.org,
holger@applied-asynchrony.com, kernel@gentoo.org,
Michal Hocko <mhocko@suse.com>
Subject: Re: OOMs on PS3 since kernel 6.9-rc4
Date: Thu, 26 Sep 2024 06:34:42 -0400 [thread overview]
Message-ID: <20240926103442.GC880690@cmpxchg.org> (raw)
In-Reply-To: <F685AEC8-34E8-4F88-91F8-1398262E8A69@yahoo.com>
Hello Damian,
On Thu, Sep 26, 2024 at 09:00:25AM +0200, Damian Dudycz wrote:
> Johannes,
>
> I have tested this with compaction enabled and it seems to be working fine now.
> I think, in that case, this should be enabled in ps3_defconfig by default.
I'm glad to hear it's working again!
> As for not having compaction in previous versions - I have been using this for pretty long
> time and Im pretty sure it used to work fine without it. Still I understand, that it should have been
> used, just mentioning that it really did work without this before that version.
Yes, it's a real regression and I believe you that it has worked until
now. My comment about luck was more in reference to the level of
support, testing and attention this configuration is getting:
config COMPACTION
bool "Allow for memory compaction"
default y
select MIGRATION
depends on MMU
help
Compaction is the only memory management component to form
high order (larger physically contiguous) memory blocks
reliably. The page allocator relies on compaction heavily and
the lack of the feature can lead to unexpected OOM killer
invocations for high order memory requests. You shouldn't
disable this option unless there really is a strong reason for
it and then we would be really interested to hear about that at
linux-mm@kvack.org.
So I definitely agree that the ps3_defconfig should be fixed.
> I’ll let ps3_defconfig maintainer know about compaction missing in ps3_defconfig
> or send patch for that config myself.
Thanks, yes this makes sense. This should be a good list of pointers:
hannes@column ~/src/linux/linux $ ./scripts/get_maintainer.pl -f arch/powerpc/configs/ps3_defconfig
Michael Ellerman <mpe@ellerman.id.au> (supporter:LINUX FOR POWERPC (32-BIT AND 64-BIT),commit_signer:2/2=100%)
Nicholas Piggin <npiggin@gmail.com> (reviewer:LINUX FOR POWERPC (32-BIT AND 64-BIT))
Christophe Leroy <christophe.leroy@csgroup.eu> (reviewer:LINUX FOR POWERPC (32-BIT AND 64-BIT))
Naveen N Rao <naveen@kernel.org> (reviewer:LINUX FOR POWERPC (32-BIT AND 64-BIT))
Geoff Levand <geoff@infradead.org> (commit_signer:2/2=100%,authored:2/2=100%,added_lines:1/1=100%,removed_lines:1/1=100%)
linuxppc-dev@lists.ozlabs.org (open list:LINUX FOR POWERPC (32-BIT AND 64-BIT))
linux-kernel@vger.kernel.org (open list)
Johannes
prev parent reply other threads:[~2024-09-26 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7CE7C8BC-D728-4A10-BD8F-15293D7CF312.ref@yahoo.com>
2024-09-24 20:52 ` Damian Dudycz
2024-09-25 17:20 ` Johannes Weiner
2024-09-25 17:43 ` Damian Dudycz
2024-09-26 7:00 ` Damian Dudycz
2024-09-26 10:34 ` Johannes Weiner [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=20240926103442.GC880690@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=damiandudycz@yahoo.com \
--cc=holger@applied-asynchrony.com \
--cc=kernel@gentoo.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=sam@gentoo.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