mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Haben <mh@ashwireless.com>
To: linux-kernel@vger.kernel.org
Subject: Memory-compaction not working on Atmel SAMA5 ARM platform, kernel v4.14 and v4.20
Date: Fri, 15 Mar 2019 10:07:53 +0000	[thread overview]
Message-ID: <bed0e6da-55be-ff26-64e7-42e62163dba5@ashwireless.com> (raw)

Hello all,


Memory-compaction is not working for me on an Atmel SAMA5D2 SoC with 
128Mbyte of RAM, on kernel versions 4.14.73. 4.14.88 and 4.20.0

Using "cat /proc/buddyinfo" to observe the state of memory 
fragmentation, and "echo 1 > /proc/sys/vm/compact_memory" to (try to) 
trigger compaction.

My kernel's /proc/config.gz includes "CONFIG_COMPACTION=y" and 
"CONFIG_MIGRATION=y"

I have rebuilt v4.20 several++ times, enabling various "CONFIG_xxx" 
items trying to enable tracing, but without success 
(/sys/kernel/debug/tracing is not present), so I haven't been able to 
observe whether the compaction-trigger is having any effect at all.


Some circumstantial evidence: memory-compaction was working on another 
ARM platform (Raspberry Pi) with kernel v4.9 (Raspbian Jessie), but 
stopped working when I dist-upgraded it to v4.14.98 (Raspbian Stretch).  
The "
/proc/sys/vm/compact_memory" device-node is present, but writing to it 
has no effect on the output from "cat /proc/buddyinfo".


So my questions are:

1.  Are "CONFIG_COMPACTION=y" + "CONFIG_MIGRATION=y" the only settings 
necessary for memory-compaction to be present and working in a kernel?  
I have Done My Own Research, but Am Not An Expert on Linux kernel features!

2.  Must I persevere with trying to get tracing working, or is there 
another way I can debug this issue?


Thank you,

Mike Haben

ASH Wireless


                 reply	other threads:[~2019-03-15 10:08 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=bed0e6da-55be-ff26-64e7-42e62163dba5@ashwireless.com \
    --to=mh@ashwireless.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®