From: "Huang\, Ying" <ying.huang@linux.intel.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Mel Gorman <mgorman@techsingularity.net>,
lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@redhat.com>,
Vitaly Wool <vitalywool@gmail.com>,
David Rientjes <rientjes@google.com>,
Christoph Lameter <cl@linux.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Vlastimil Babka <vbabka@suse.cz>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [lkp] [mm, page_alloc] 43993977ba: +88% OOM possibility
Date: Fri, 30 Oct 2015 16:21:40 +0800 [thread overview]
Message-ID: <87si4szrzf.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20151029142440.GE23598@dhcp22.suse.cz> (Michal Hocko's message of "Thu, 29 Oct 2015 15:24:40 +0100")
[-- Attachment #1: Type: text/plain, Size: 565 bytes --]
Michal Hocko <mhocko@kernel.org> writes:
> On Wed 28-10-15 13:36:02, kernel test robot wrote:
>> FYI, we noticed the below changes on
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> commit 43993977baecd838d66ccabc7f682342fc6ff635 ("mm, page_alloc:
>> distinguish between being unable to sleep, unwilling to sleep and
>> avoiding waking kswapd")
>>
>> We found the OOM possibility increased 88% in a virtual machine with 1G memory.
>
> Could you provide dmesg output from this test?
Sure, Attached.
Best Regards,
Huang, Ying
[-- Attachment #2: dmesg.xz --]
[-- Type: application/x-xz, Size: 32456 bytes --]
next prev parent reply other threads:[~2015-10-30 8:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 5:36 kernel test robot
2015-10-29 14:24 ` Michal Hocko
2015-10-30 8:21 ` Huang, Ying [this message]
2015-10-30 10:38 ` Michal Hocko
2015-11-01 23:20 ` Huang, Ying
2015-11-02 7:45 ` Michal Hocko
2015-11-02 8:55 ` Huang, Ying
2015-11-02 9:53 ` Michal Hocko
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=87si4szrzf.fsf@yhuang-dev.intel.com \
--to=ying.huang@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=sfr@canb.auug.org.au \
--cc=vbabka@suse.cz \
--cc=vitalywool@gmail.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
Powered by JetHome