From: chenridong <chenridong@huawei.com>
To: Matthew Wilcox <willy@infradead.org>,
Barry Song <21cnbao@gmail.com>, Chris Li <chrisl@kernel.org>
Cc: Chen Ridong <chenridong@huaweicloud.com>,
<akpm@linux-foundation.org>, <mhocko@suse.com>,
<hannes@cmpxchg.org>, <yosryahmed@google.com>,
<yuzhao@google.com>, <david@redhat.com>, <ryan.roberts@arm.com>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<wangweiyang2@huawei.com>, <xieym_ict@hotmail.com>,
Chris Li <chrisl@kernel.org>
Subject: Re: [RFC PATCH v2 1/1] mm/vmscan: move the written-back folios to the tail of LRU after shrinking
Date: Mon, 25 Nov 2024 09:19:11 +0800 [thread overview]
Message-ID: <7e617fe7-388f-43a1-b0fa-e2998194b90c@huawei.com> (raw)
In-Reply-To: <ZzrA5nXldoE2PWx4@casper.infradead.org>
On 2024/11/18 12:21, Matthew Wilcox wrote:
> On Mon, Nov 18, 2024 at 05:14:14PM +1300, Barry Song wrote:
>> On Mon, Nov 18, 2024 at 5:03 PM Matthew Wilcox <willy@infradead.org> wrote:
>>>
>>> On Sat, Nov 16, 2024 at 09:16:58AM +0000, Chen Ridong wrote:
>>>> 2. In shrink_page_list function, if folioN is THP(2M), it may be splited
>>>> and added to swap cache folio by folio. After adding to swap cache,
>>>> it will submit io to writeback folio to swap, which is asynchronous.
>>>> When shrink_page_list is finished, the isolated folios list will be
>>>> moved back to the head of inactive lru. The inactive lru may just look
>>>> like this, with 512 filioes have been move to the head of inactive lru.
>>>
>>> I was hoping that we'd be able to stop splitting the folio when adding
>>> to the swap cache. Ideally. we'd add the whole 2MB and write it back
>>> as a single unit.
>>
>> This is already the case: adding to the swapcache doesn’t require splitting
>> THPs, but failing to allocate 2MB of contiguous swap slots will.
>
> Agreed we need to understand why this is happening. As I've said a few
> times now, we need to stop requiring contiguity. Real filesystems don't
> need the contiguity (they become less efficient, but they can scatter a
> single 2MB folio to multiple places).
>
> Maybe Chris has a solution to this in the works?
>
Hi, Chris, do you have a better idea to solve this issue?
Best regards,
Ridong
next prev parent reply other threads:[~2024-11-25 1:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 9:16 [RFC PATCH v2 0/1] " Chen Ridong
2024-11-16 9:16 ` [RFC PATCH v2 1/1] " Chen Ridong
2024-11-17 3:26 ` Barry Song
2024-11-18 2:18 ` Chen Ridong
2024-11-18 4:03 ` Matthew Wilcox
2024-11-18 4:14 ` Barry Song
2024-11-18 4:21 ` Matthew Wilcox
2024-11-25 1:19 ` chenridong [this message]
2024-11-28 23:08 ` Barry Song
2024-11-29 2:25 ` chenridong
2024-11-29 3:07 ` Barry Song
2024-11-27 0:08 ` Chris Li
2024-11-18 9:41 ` chenridong
2024-11-18 9:55 ` Barry Song
2024-11-27 0:17 ` Chris Li
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=7e617fe7-388f-43a1-b0fa-e2998194b90c@huawei.com \
--to=chenridong@huawei.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chenridong@huaweicloud.com \
--cc=chrisl@kernel.org \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=ryan.roberts@arm.com \
--cc=wangweiyang2@huawei.com \
--cc=willy@infradead.org \
--cc=xieym_ict@hotmail.com \
--cc=yosryahmed@google.com \
--cc=yuzhao@google.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
all inboxes | Powered by JetHome®