From: Michal Hocko <mhocko@kernel.org>
To: Aaron Lu <aaron.lu@intel.com>
Cc: "Huang, Ying" <ying.huang@intel.com>,
kernel test robot <xiaolong.ye@intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Hillf Danton <hillf.zj@alibaba-inc.com>,
LKML <linux-kernel@vger.kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Mel Gorman <mgorman@suse.de>,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
lkp@01.org, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-mm@kvack.org
Subject: Re: [LKP] [lkp] [mm, oom] faad2185f4: vm-scalability.throughput -11.8% regression
Date: Fri, 29 Apr 2016 15:00:55 +0200 [thread overview]
Message-ID: <20160429130055.GN21977@dhcp22.suse.cz> (raw)
In-Reply-To: <20160429125413.GA21824@aaronlu.sh.intel.com>
On Fri 29-04-16 20:54:13, Aaron Lu wrote:
> On Fri, Apr 29, 2016 at 11:29:36AM +0200, Michal Hocko wrote:
> > On Fri 29-04-16 16:59:37, Aaron Lu wrote:
> > > On Thu, Apr 28, 2016 at 01:21:35PM +0200, Michal Hocko wrote:
> > > > All of them are order-2 and this was a known problem for "mm, oom:
> > > > rework oom detection" commit and later should make it much more
> > > > resistant to failures for higher (!costly) orders. So I would definitely
> > > > encourage you to retest with the current _complete_ mmotm tree.
> > >
> > > OK, will run the test on this branch:
> > > https://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git since-4.5
> > > with head commit:
> > > commit 81cc2e6f1e8bd81ebc7564a3cd3797844ee1712e
> > > Author: Michal Hocko <mhocko@suse.com>
> > > Date: Thu Apr 28 12:03:24 2016 +0200
> > >
> > > drm/amdgpu: make amdgpu_mn_get wait for mmap_sem killable
> > >
> > > Please let me know if this isn't right.
> >
> > Yes that should contain all the oom related patches in the mmotm tree.
>
> The test shows commit 81cc2e6f1e doesn't OOM anymore and its throughput
> is 43609, the same level compared to 43802, so everyting is fine :-)
Thanks a lot for double checking! This is highly appreciated!
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-04-29 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160427031556.GD29014@yexl-desktop>
[not found] ` <20160427073617.GA2179@dhcp22.suse.cz>
[not found] ` <87fuu7iht0.fsf@yhuang-dev.intel.com>
[not found] ` <20160427083733.GE2179@dhcp22.suse.cz>
[not found] ` <87bn4vigpc.fsf@yhuang-dev.intel.com>
[not found] ` <20160427091718.GG2179@dhcp22.suse.cz>
2016-04-28 5:17 ` [LKP] [lkp] [mm, oom] faad2185f4: vm-scalability.throughput -11.8% regression Aaron Lu
2016-04-28 8:57 ` Michal Hocko
2016-04-28 9:45 ` Aaron Lu
2016-04-28 11:21 ` Michal Hocko
2016-04-29 8:59 ` Aaron Lu
2016-04-29 9:29 ` Michal Hocko
2016-04-29 12:54 ` Aaron Lu
2016-04-29 13:00 ` Michal Hocko [this message]
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=20160429130055.GN21977@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=aaron.lu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hillf.zj@alibaba-inc.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@01.org \
--cc=mgorman@suse.de \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=rientjes@google.com \
--cc=sfr@canb.auug.org.au \
--cc=xiaolong.ye@intel.com \
--cc=ying.huang@intel.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).