From: Joonsoo Kim <js1304@gmail.com>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>, Hugh Dickins <hughd@google.com>,
Minchan Kim <minchan@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
Mel Gorman <mgorman@techsingularity.net>,
kernel-team@lge.com, Joonsoo Kim <iamjoonsoo.kim@lge.com>,
lkp@lists.01.org
Subject: Re: [mm/workingset] 323c95f095: fio.read_bw_MBps 19.5% improvement
Date: Fri, 28 Feb 2020 19:03:58 +0900 [thread overview]
Message-ID: <CAAmzW4NzT5G5ef9vFsU_=zV8+UyJHuRjfwKBbqij9kNd8wV8PQ@mail.gmail.com> (raw)
In-Reply-To: <20200228074200.GL6548@shao2-debian>
2020년 2월 28일 (금) 오후 4:42, kernel test robot <rong.a.chen@intel.com>님이 작성:
>
> Greeting,
>
> FYI, we noticed a 19.5% improvement of fio.read_bw_MBps due to commit:
Hello, all.
Please forget this improvement report.
My revision 1 patchset has a bug on this patch and it looks like it
causes some improvement. :)
I have fixed this bug at revision 2 patchset.
Thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Joonsoo Kim <js1304@gmail.com>
To: lkp@lists.01.org
Subject: Re: [mm/workingset] 323c95f095: fio.read_bw_MBps 19.5% improvement
Date: Fri, 28 Feb 2020 19:03:58 +0900 [thread overview]
Message-ID: <CAAmzW4NzT5G5ef9vFsU_=zV8+UyJHuRjfwKBbqij9kNd8wV8PQ@mail.gmail.com> (raw)
In-Reply-To: <20200228074200.GL6548@shao2-debian>
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
2020년 2월 28일 (금) 오후 4:42, kernel test robot <rong.a.chen@intel.com>님이 작성:
>
> Greeting,
>
> FYI, we noticed a 19.5% improvement of fio.read_bw_MBps due to commit:
Hello, all.
Please forget this improvement report.
My revision 1 patchset has a bug on this patch and it looks like it
causes some improvement. :)
I have fixed this bug at revision 2 patchset.
Thanks.
next prev parent reply other threads:[~2020-02-28 10:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 6:19 [PATCH 0/9] workingset protection/detection on the anonymous LRU list js1304
2020-02-11 6:19 ` [PATCH 1/9] mm/vmscan: make active/inactive ratio as 1:1 for anon lru js1304
2020-02-27 2:29 ` [mm/vmscan] dcf33bfdfb: vm-scalability.median 402.4% improvement kernel test robot
2020-02-27 2:29 ` kernel test robot
2020-02-11 6:19 ` [PATCH 2/9] mm/vmscan: protect the workingset on anonymous LRU js1304
2020-02-11 6:19 ` [PATCH 3/9] mm/workingset: extend the workingset detection for anon LRU js1304
2020-02-14 4:07 ` Joonsoo Kim
2020-02-14 4:07 ` Joonsoo Kim
2020-02-28 7:42 ` [mm/workingset] 323c95f095: fio.read_bw_MBps 19.5% improvement kernel test robot
2020-02-28 7:42 ` kernel test robot
2020-02-28 10:03 ` Joonsoo Kim [this message]
2020-02-28 10:03 ` Joonsoo Kim
2020-02-28 10:03 ` Joonsoo Kim
2020-02-11 6:19 ` [PATCH 4/9] mm/swapcache: support to handle the value in swapcache js1304
2020-02-11 6:19 ` [PATCH 5/9] mm/workingset: use the node counter if memcg is the root memcg js1304
2020-02-11 6:19 ` [PATCH 6/9] mm/workingset: handle the page without memcg js1304
2020-02-11 6:19 ` [PATCH 7/9] mm/swap: implement workingset detection for anonymous LRU js1304
2020-02-11 6:19 ` [PATCH 8/9] mm/vmscan: restore active/inactive ratio " js1304
2020-02-11 6:19 ` [PATCH 9/9] mm/swap: count a new anonymous page as a reclaim_state's rotate js1304
2020-02-12 3:35 ` Hillf Danton
2020-02-12 11:00 ` Joonsoo Kim
2020-02-12 11:00 ` Joonsoo Kim
2020-02-14 4:12 ` [PATCH 0/9] workingset protection/detection on the anonymous LRU list Joonsoo Kim
2020-02-14 4:12 ` Joonsoo Kim
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='CAAmzW4NzT5G5ef9vFsU_=zV8+UyJHuRjfwKBbqij9kNd8wV8PQ@mail.gmail.com' \
--to=js1304@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@lists.01.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=minchan@kernel.org \
--cc=rong.a.chen@intel.com \
--cc=vbabka@suse.cz \
/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.