From: Luigi Semenzato <semenzato@google.com>
To: linux-mm@kvack.org, Nitin Gupta <ngupta@vflare.org>,
Seth Jennings <sjenning@linux.vnet.ibm.com>
Subject: zram on ARM
Date: Fri, 2 Nov 2012 12:59:13 -0700 [thread overview]
Message-ID: <CAA25o9SD8cZUaVT-SA2f9NVvPdmYo++WGn8Gfie3bhkrc8dCxQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1507 bytes --]
Does anybody have any information on the status of zram on ARM?
Specifically, how much it has been tested.
I noticed that zram and zsmalloc on ToT no longer have the x86
restriction, and they compile fine on our 3.4 branch. Sadly, that's
where my luck ends.
When I run my standard Chrome load (which just opens a bunch of
memory-intensive browser tabs), Chrome dies shortly after the system
starts swapping pages out. For instance, here's are the SI and SO
fields of "vmstat 1":
si so
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 168
0 0
0 924
188 26332
520 30672
1304 32208
2360 30804
18836 24832
<--- chrome dies here
6496 0
892 0
260 0
8 0
I also have a simpler load: a program that allocates memory non-stop,
and fills part of it with data from /dev/urandom (to simulate the
observed compressibility). The program never reads its data though, so
it doesn't get swapped back in, as in the previous load. This runs
for a while and partially fills the swap device, then the system
hangs.
Deja vu, eh? I am running this with my patch, which may result in
extra OOM kills. Interestingly, a few threads are blocked in
exit_mm(), but not on a page fault. Most processes are in
congestion_wait(), so this is probably not the same situation I was
seeing earlier.
Anyway, I am attaching the output of SysRQ-X with lots of stack
traces. Thank you very much for any information!
Luigi
[-- Attachment #2: console-ramoops58 --]
[-- Type: application/octet-stream, Size: 131072 bytes --]
next reply other threads:[~2012-11-02 19:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 19:59 Luigi Semenzato [this message]
2012-11-02 20:52 ` zram on ARM Luigi Semenzato
2012-11-02 22:53 ` Minchan Kim
2012-11-02 23:27 ` Luigi Semenzato
2012-11-03 0:04 ` Luigi Semenzato
2012-11-03 0:09 ` Luigi Semenzato
2012-11-05 21:12 ` Luigi Semenzato
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=CAA25o9SD8cZUaVT-SA2f9NVvPdmYo++WGn8Gfie3bhkrc8dCxQ@mail.gmail.com \
--to=semenzato@google.com \
--cc=linux-mm@kvack.org \
--cc=ngupta@vflare.org \
--cc=sjenning@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).