From: "Lu, Aaron" <aaron.lu@intel.com>
To: "akpm@linux-foundation.org" <akpm@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tim.c.chen@linux.intel.com" <tim.c.chen@linux.intel.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"ak@linux.intel.com" <ak@linux.intel.com>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"Wang, Kemi" <kemi.wang@intel.com>,
"mhocko@suse.com" <mhocko@suse.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
"mgorman@techsingularity.net" <mgorman@techsingularity.net>,
"Huang, Ying" <ying.huang@intel.com>
Subject: Re: [RFC PATCH] mm, page_alloc: double zone's batchsize
Date: Thu, 12 Jul 2018 01:40:41 +0000 [thread overview]
Message-ID: <9f778198327e62cdab0651382740189e0665507a.camel@intel.com> (raw)
In-Reply-To: <20180711143505.5ccb378fb67dc6ba8fa202a3@linux-foundation.org>
On Wed, 2018-07-11 at 14:35 -0700, Andrew Morton wrote:
> On Wed, 11 Jul 2018 13:58:55 +0800 Aaron Lu <aaron.lu@intel.com> wrote:
>
> > [550 lines of changelog]
>
> OK, I'm convinced ;) That was a lot of work - thanks for being exhaustive.
Thanks Andrew.
I think the credit goes to Dave Hansen since he has been very careful
about this change and would like me to do all those 2nd phase tests to
make sure we didn't get any surprise after doubling batch size :-)
I think the LKP robot will run even more tests to capture possible
regressions, if any.
next prev parent reply other threads:[~2018-07-12 1:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 5:58 [RFC PATCH] mm, page_alloc: double zone's batchsize Aaron Lu
2018-07-11 21:35 ` Andrew Morton
2018-07-12 1:40 ` Lu, Aaron [this message]
2018-07-12 1:46 ` Andrew Morton
2018-07-12 12:54 ` Michal Hocko
2018-07-12 13:55 ` Jesper Dangaard Brouer
2018-07-12 15:01 ` Tariq Toukan
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=9f778198327e62cdab0651382740189e0665507a.camel@intel.com \
--to=aaron.lu@intel.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=kemi.wang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=tim.c.chen@linux.intel.com \
--cc=vbabka@suse.cz \
--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).