From: Joonsoo Kim <js1304@gmail.com>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [mm/cma] 2b0f904a5a: fio.read_bw_MBps -16.1% regression
Date: Mon, 09 Apr 2018 16:25:52 +0900 [thread overview]
Message-ID: <CAAmzW4MHjvDrDdoeSf3imjRboCA+Z4yTaDF=WsS3vsjYUCiVUw@mail.gmail.com> (raw)
In-Reply-To: <20180409055619.GC27349@yexl-desktop>
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
2018-04-09 14:56 GMT+09:00 Ye Xiaolong <xiaolong.ye@intel.com>:
> On 04/05, Joonsoo Kim wrote:
>>I may find the reason of this regression. Could you test this patch on
>>top of this patchset?
>>
>>http://lkml.kernel.org/r/<1522913236-15776-1-git-send-email-iamjoonsoo.kim@lge.com>
>
> It'd be better if you can provide your repo for this fix patch, it's more
> convenient for 0day to verify it.
Okay! Could you check following git tree and branch to fix the
reported regression?
https://github.com/JoonsooKim/linux.git cma-fixup-thp-next-20180403
Related commits are:
f11152b mm/thp: don't count ZONE_MOVABLE as the target for freepage reserving
b2adb03 Revert "Revert "mm/cma: manage the memory of the CMA area by
using the ZONE_MOVABLE""
76148e2 Revert "Revert "mm/page_alloc: don't reserve ZONE_HIGHMEM for
ZONE_MOVABLE request""
Base commit is '76148e2' and this regression happens on 'b2adb03'.
Fix is commit 'f11152b'.
Thanks.
next prev parent reply other threads:[~2018-04-09 7:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 6:35 [lkp-robot] [mm/cma] 2b0f904a5a: fio.read_bw_MBps -16.1% regression kernel test robot
2018-01-02 6:35 ` kernel test robot
2018-01-03 2:05 ` Joonsoo Kim
2018-01-03 2:05 ` Joonsoo Kim
2018-01-06 9:26 ` Ye Xiaolong
2018-01-06 9:26 ` Ye Xiaolong
2018-01-09 7:16 ` Joonsoo Kim
2018-01-09 7:16 ` Joonsoo Kim
2018-04-05 7:48 ` Joonsoo Kim
2018-04-05 7:48 ` Joonsoo Kim
2018-04-09 5:56 ` Ye Xiaolong
2018-04-09 7:25 ` Joonsoo Kim [this message]
2018-04-09 7:40 ` Ye Xiaolong
2018-04-12 1:12 ` Ye Xiaolong
2018-04-12 1:26 ` Joonsoo Kim
2018-04-13 1:18 ` Ye Xiaolong
2018-04-23 6:39 ` Joonsoo Kim
2018-05-03 4:46 ` Ye Xiaolong
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='CAAmzW4MHjvDrDdoeSf3imjRboCA+Z4yTaDF=WsS3vsjYUCiVUw@mail.gmail.com' \
--to=js1304@gmail.com \
--cc=lkp@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.