From: CAI Qian <caiqian@redhat.com>
To: David Rientjes <rientjes@google.com>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: known oom issues on numa in -mm tree?
Date: Fri, 28 Jan 2011 01:47:35 -0500 (EST) [thread overview]
Message-ID: <1830247931.201921.1296197255760.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1101260244310.27469@chino.kir.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 748 bytes --]
----- Original Message -----
> On Tue, 11 Jan 2011, CAI Qian wrote:
>
> > BTW, the latest linux-next also had the similar issue.
> >
> > - kswapd was running for a long time.
> >
>
> I'd be interested to see if this is fixed now that 2ff754fa8f41 (mm:
> clear
> pages_scanned only if draining a pcp adds pages to the buddy
> allocator)
> has been merged in Linus' tree.
I can still reproduce this similar failure on both AMD and Intel NUMA
systems using the latest linus tree with the commit you mentioned.
Unfortunately, I can't get a clear sysrq/console output of it but only
a part of it (screenshot attached).
It at least very easy to reproduce it for me by running LTP oom01 test
for both Magny-Cours and Nehalem-EX NUMA systems.
CAI Qian
[-- Attachment #2: Screenshot.png --]
[-- Type: image/png, Size: 265476 bytes --]
next prev parent reply other threads:[~2011-01-28 6:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 8:03 known oom issues on numa in -mm tree? CAI Qian
2011-01-11 0:04 ` David Rientjes
2011-01-11 1:36 ` CAI Qian
2011-01-11 3:18 ` David Rientjes
2011-01-11 3:35 ` CAI Qian
2011-01-11 9:46 ` CAI Qian
2011-01-11 9:55 ` CAI Qian
2011-01-11 10:11 ` CAI Qian
2011-01-26 10:45 ` David Rientjes
2011-01-28 6:47 ` CAI Qian [this message]
2011-01-28 10:31 ` David Rientjes
2011-01-28 14:33 ` CAI Qian
2011-01-28 14:36 ` CAI Qian
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=1830247931.201921.1296197255760.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com \
--to=caiqian@redhat.com \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.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).