From: Breno Leitao <leitao@debian.org>
To: "黄朝阳 (Zhaoyang Huang)" <zhaoyang.huang@unisoc.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Matthew Wilcox" <willy@infradead.org>,
"Suren Baghdasaryan" <surenb@google.com>,
"Minchan Kim" <minchan@kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Zhaoyang Huang" <huangzhaoyang@gmail.com>,
"王科 (Ke Wang)" <Ke.Wang@unisoc.com>,
"usamaarif642@gmail.com" <usamaarif642@gmail.com>,
"riel@surriel.com" <riel@surriel.com>,
"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
"nphamcs@gmail.com" <nphamcs@gmail.com>
Subject: Re: reply: [PATCHv5] mm: skip CMA pages when they are not available
Date: Fri, 16 Aug 2024 10:20:03 -0700 [thread overview]
Message-ID: <Zr+KQ4/iiIqmkUSk@gmail.com> (raw)
In-Reply-To: <a74760bd1d81467db2a03b77d3aef7d3@BJMBX01.spreadtrum.com>
Hello Zhaoyang,
On Tue, Aug 13, 2024 at 09:58:32AM +0000, 黄朝阳 (Zhaoyang Huang) wrote:
> >I've been discussing this with colleagues and we're speculating that the high
> >contention might be linked to the fact that CMA regions are now being skipped.
> >This could potentially extend the duration of the
> >isolate_lru_folios() 'while' loop, resulting in increased pressure on the lock.
> >However, I want to emphasize that I'm not an expert in this area and I am
> >simply sharing the data I collected.
> Could you please try below patch which could be helpful
>
> https://lore.kernel.org/linux-mm/CAOUHufa7OBtNHKMhfu8wOOE4f0w3b0_2KzzV7-hrc9rVL8e=iw@mail.gmail.com/
Yes, my colleague Usama have tried it, and it solved the problem. Thanks
for the heads-up, it was very useful.
--breno
prev parent reply other threads:[~2024-08-16 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 9:58 黄朝阳 (Zhaoyang Huang)
2024-08-16 17:20 ` Breno Leitao [this message]
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=Zr+KQ4/iiIqmkUSk@gmail.com \
--to=leitao@debian.org \
--cc=Ke.Wang@unisoc.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=huangzhaoyang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=nphamcs@gmail.com \
--cc=riel@surriel.com \
--cc=surenb@google.com \
--cc=usamaarif642@gmail.com \
--cc=willy@infradead.org \
--cc=zhaoyang.huang@unisoc.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