From: Rik van Riel <riel@redhat.com>
To: Mel Gorman <mgorman@techsingularity.net>,
kernel test robot <ying.huang@linux.intel.com>
Cc: lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Vitaly Wool <vitalywool@gmail.com>,
David Rientjes <rientjes@google.com>,
Christoph Lameter <cl@linux.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [lkp] [mm, page_alloc] d0164adc89: -100.0% fsmark.app_overhead
Date: Thu, 26 Nov 2015 10:03:01 -0500 [thread overview]
Message-ID: <56571F25.5030905@redhat.com> (raw)
In-Reply-To: <20151126132511.GG14880@techsingularity.net>
On 11/26/2015 08:25 AM, Mel Gorman wrote:
> On Thu, Nov 26, 2015 at 08:56:12AM +0800, kernel test robot wrote:
>> FYI, we noticed the below changes on
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> commit d0164adc89f6bb374d304ffcc375c6d2652fe67d ("mm, page_alloc: distinguish between being unable to sleep, unwilling to sleep and avoiding waking kswapd")
>>
>> Note: the testing machine is a virtual machine with only 1G memory.
>>
>
> I'm not actually seeing any problem here. Is this a positive report or
> am I missing something obvious?
I've gotten several reports that could be either
positive or negative, but where I am not quite
sure how to interpret the results.
The tool seems to CC the maintainers of the code
that was changed, so I am hoping they will pipe
up when they see a problem.
Of course, that doesn't help in this case :)
next prev parent reply other threads:[~2015-11-26 15:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 0:56 kernel test robot
2015-11-26 13:25 ` Mel Gorman
2015-11-26 15:03 ` Rik van Riel [this message]
2015-11-27 1:14 ` Huang, Ying
2015-11-27 10:06 ` Mel Gorman
2015-11-30 2:14 ` Huang, Ying
2015-11-30 13:02 ` Michal Hocko
2015-12-01 12:23 ` Will Deacon
2015-12-01 14:04 ` Michal Hocko
2015-12-02 11:10 ` Mel Gorman
2015-12-02 11:00 ` Mel Gorman
2015-12-02 12:00 ` Michal Hocko
2015-12-02 14:08 ` Mel Gorman
2015-12-02 14:15 ` Michal Hocko
2015-12-02 14:45 ` Mel Gorman
2015-12-03 8:46 ` Huang, Ying
2015-12-03 10:17 ` Mel Gorman
2015-12-04 1:53 ` Huang, Ying
2015-12-07 16:18 ` 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=56571F25.5030905@redhat.com \
--to=riel@redhat.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@suse.com \
--cc=rientjes@google.com \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=vitalywool@gmail.com \
--cc=ying.huang@linux.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
Powered by JetHome