From: Michal Hocko <mhocko@suse.com>
To: David Hildenbrand <david@redhat.com>
Cc: zhou <xianrong_zhou@163.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, mgorman@suse.de,
willy@linux.intel.com, rostedt@goodmis.org, mingo@redhat.com,
vbabka@suse.cz, rientjes@google.com,
pankaj.gupta.linux@gmail.com, bhe@redhat.com,
ying.huang@intel.com, iamjoonsoo.kim@lge.com, minchan@kernel.org,
ruxian.feng@transsion.com, kai.cheng@transsion.com,
zhao.xu@transsion.com, zhouxianrong@tom.com,
zhou xianrong <xianrong.zhou@transsion.com>
Subject: Re: [PATCH] kswapd: no need reclaim cma pages triggered by unmovable allocation
Date: Mon, 15 Mar 2021 17:09:23 +0100 [thread overview]
Message-ID: <YE+Gs13F8nV1Z1/d@dhcp22.suse.cz> (raw)
In-Reply-To: <64f8c03f-7fd9-2e03-6b90-67e2a5a45b9d@redhat.com>
On Mon 15-03-21 16:46:33, David Hildenbrand wrote:
> On 13.03.21 09:31, zhou wrote:
[...]
> > This optimization can avoid ~3% unnecessary isolations from cma
> > (cma isolated / total isolated) with configuration of total 100Mb
> > cma pages.
>
> Can you say a few words about interaction with ZONE_MOVABLE, which behaves
> similar to CMA? I.e., does the same apply to ZONE_MOVABLE? Is it already
> handled?
No, the movable zone shouldn't be affected as the reclaim is zone aware.
The problem is that CMA doesn't belong to any particular zone. This is
something Joonsoo worked in the past and I believe following up on that
work has been recommended last time a similar/same approach like this
patch was proposed.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2021-03-15 16:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 8:31 zhou
2021-03-13 10:50 ` kernel test robot
2021-03-15 15:46 ` David Hildenbrand
2021-03-15 16:09 ` Michal Hocko [this message]
2021-03-15 16:12 ` David Hildenbrand
2021-03-16 1:57 ` zhou xianrong
-- strict thread matches above, loose matches on Subject: below --
2021-02-09 8:23 zhou
2021-02-09 9:23 ` Michal Hocko
2021-02-10 4:07 ` zhou xianrong
2021-02-10 13:14 ` Michal Hocko
2021-02-11 1:58 ` zhouxianrong
2021-02-11 11:01 ` zhou xianrong
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=YE+Gs13F8nV1Z1/d@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=david@redhat.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kai.cheng@transsion.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=mingo@redhat.com \
--cc=pankaj.gupta.linux@gmail.com \
--cc=rientjes@google.com \
--cc=rostedt@goodmis.org \
--cc=ruxian.feng@transsion.com \
--cc=vbabka@suse.cz \
--cc=willy@linux.intel.com \
--cc=xianrong.zhou@transsion.com \
--cc=xianrong_zhou@163.com \
--cc=ying.huang@intel.com \
--cc=zhao.xu@transsion.com \
--cc=zhouxianrong@tom.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