From: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Hamish Martin <Hamish.Martin@alliedtelesis.co.nz>
Subject: Per-process memory usage increased between kernel 4.4.x and 5.6
Date: Sun, 19 Jul 2020 22:30:30 +0000 [thread overview]
Message-ID: <fa4134a6-c4fe-344b-cdfb-81cc07ac97c6@alliedtelesis.co.nz> (raw)
Hi,
Not sure exactly where to direct this so I'm just hitting linux-mm and
linux-kernel and hoping someone sees it.
We're in the process of updating our embedded targets from Linux 4.4.x
to the latest kernel (currently v5.6 but we're planning to go to v5.7
and maybe v5.8 depending on timing).
We've hit an issue where across multiple architectures (at least arm,
mips and powerpc) we're seeing a significant decrease in the amount of
Free/Available memory (40 to 90 MB). It seems to get worse with more
processes running but no single process is consuming a significantly
greater amount of memory.
Is anyone able to provide some hints as to where we should investigate
or what in the kernel might have a per-process impact on memory used.
Thanks,
Chris
reply other threads:[~2020-07-19 22:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=fa4134a6-c4fe-344b-cdfb-81cc07ac97c6@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=Hamish.Martin@alliedtelesis.co.nz \
--cc=linux-kernel@vger.kernel.org \
--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.