From: Mike Rapoport <rppt@kernel.org>
To: "Pratoussy, Martin (GE Vernova)" <Martin.PRATOUSSY@ge.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"Kurtz1, Florian (GE Vernova)" <Florian.Kurtz1@ge.com>
Subject: Re: Disabling CONFIG_COMPACTION
Date: Wed, 17 May 2023 13:02:20 +0300 [thread overview]
Message-ID: <20230517100220.GB4967@kernel.org> (raw)
In-Reply-To: <BL1P101MB050903FE79CFA3804EA83855E0789@BL1P101MB0509.NAMP101.PROD.OUTLOOK.COM>
Hi,
On Mon, May 15, 2023 at 08:44:30AM +0000, Pratoussy, Martin (GE Vernova) wrote:
> Hello,
>
> We are facing an issue regarding Linux kernel 5.10.153. When we try to
> allocate huge amount of memory, we eventually run prematurely out of
> memory. The bug has been discovered as follows: although "free" and
> "top" commands would show 40 MB of free memory, sending a 32 MB file
> through SFTP into RAM cache will lead to an OOM error before finishing
> the transfer.
> It has been noted that the command "echo 1 > /prox/sys/vm/compact_memory"
> leads into the very same behavior of the kernel. Disabling
> CONFIG_COMPACTION is surprisingly resolving the allocation issue and we
> are trying to understand why.
>
> You will find below more information about the error we are facing:
>
> * Architecture: Nios2
> * Total RAM size: 64 MB
> * Available RAM size when error occurs: ~17MB
> * Error message: "Huh VM_FAULT_OOM leaked out to the #PF handler. Retrying PF"
>
> Would you have any idea of what is happening?
Even without digging into the actual reason for OOM, it makes perfect sense
to disable compaction on your system.
> You will find attached the .config of our kernel.
>
> Best regards,
>
> Martin Pratoussy
> Embedded software engineer apprentice - Electronics & High Voltage Digital, Grid Solutions
> GE Renewable
> M +33 (0)7 82 54 60 81
> www.gegridsolutions.com<http://www.gegridsolutions.com>
> 21, Rue Cyprian | 69100 Villeurbanne | France
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2023-05-17 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 8:44 Disabling CONFIG_COMPACTION Pratoussy, Martin (GE Vernova)
2023-05-17 10:02 ` Mike Rapoport [this message]
[not found] ` <SA0P101MB0500A58EE4AB7E0F1B9310ECE0439@SA0P101MB0500.NAMP101.PROD.OUTLOOK.COM>
2023-05-23 7:09 ` EXT: " Mike Rapoport
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=20230517100220.GB4967@kernel.org \
--to=rppt@kernel.org \
--cc=Florian.Kurtz1@ge.com \
--cc=Martin.PRATOUSSY@ge.com \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.