From: Yafang Shao <laoar.shao@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: akpm@linux-foundation.org, hannes@cmpxchg.org, mhocko@kernel.org,
roman.gushchin@linux.dev, shakeelb@google.com,
muchun.song@linux.dev, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC PATCH] mm: Add reclaim type to memory.reclaim
Date: Mon, 26 Feb 2024 21:56:39 +0800 [thread overview]
Message-ID: <CALOAHbB2UiZ_XCPzhsHJF1HqOcDPjoJi+bA9yi7MnAgdEvNkUA@mail.gmail.com> (raw)
In-Reply-To: <ZdyPPiEykhffDEJZ@casper.infradead.org>
On Mon, Feb 26, 2024 at 9:16 PM Matthew Wilcox <willy@infradead.org> wrote:
>
> On Mon, Feb 26, 2024 at 08:34:07PM +0800, Yafang Shao wrote:
> > Additionally, since this patch offers a straightforward solution to
> > address the issue in container environments, would it be feasible to
> > apply this patch initially?
>
> There are lot sof other problems with this patch, but since I disagree
> with the idea of this patch, I didn't enumerate them.
Could you please provide an enumeration of the issues you've
identified? One issue is that the reclaimed bytes may not be optimal
for slab shrinking, particularly because many dentries are freed
deferredly.
--
Regards
Yafang
next prev parent reply other threads:[~2024-02-26 13:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 11:42 Yafang Shao
2024-02-26 4:17 ` Matthew Wilcox
2024-02-26 12:34 ` Yafang Shao
2024-02-26 13:16 ` Matthew Wilcox
2024-02-26 13:56 ` Yafang Shao [this message]
2024-02-26 14:04 ` Michal Hocko
2024-02-27 5:48 ` Yafang Shao
2024-02-27 9:05 ` Michal Hocko
2024-02-27 9:39 ` Yafang Shao
2024-02-27 9:43 ` Yosry Ahmed
2024-02-27 11:37 ` Yafang Shao
2024-02-27 11:40 ` Yosry Ahmed
2024-02-27 11:58 ` Yafang Shao
2024-02-27 12:09 ` Yafang Shao
2024-02-27 12:12 ` Yafang Shao
2024-02-27 13:17 ` Michal Hocko
2024-02-27 14:05 ` Yafang Shao
2024-02-27 9:45 ` Michal Hocko
2024-02-27 10:06 ` Yafang Shao
2024-02-27 13:20 ` Michal Hocko
2024-02-27 14:03 ` Yafang Shao
2024-02-27 14:51 ` Yafang Shao
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=CALOAHbB2UiZ_XCPzhsHJF1HqOcDPjoJi+bA9yi7MnAgdEvNkUA@mail.gmail.com \
--to=laoar.shao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeelb@google.com \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox