All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kairui Song <ryncsn@gmail.com>
To: Barry Song <baohua@kernel.org>
Cc: kasong@tencent.com, linux-mm@kvack.org,
	 Andrew Morton <akpm@linux-foundation.org>,
	Axel Rasmussen <axelrasmussen@google.com>,
	 Yuanchu Xie <yuanchu@google.com>, Wei Xu <weixugc@google.com>,
	 Johannes Weiner <hannes@cmpxchg.org>,
	David Hildenbrand <david@kernel.org>,
	 Michal Hocko <mhocko@kernel.org>,
	Qi Zheng <zhengqi.arch@bytedance.com>,
	 Shakeel Butt <shakeel.butt@linux.dev>,
	Lorenzo Stoakes <ljs@kernel.org>,
	 David Stevens <stevensd@google.com>,
	Chen Ridong <chenridong@huaweicloud.com>,
	 Leno Hou <lenohou@gmail.com>, Yafang Shao <laoar.shao@gmail.com>,
	Yu Zhao <yuzhao@google.com>,
	 Zicheng Wang <wangzicheng@honor.com>,
	Kalesh Singh <kaleshsingh@google.com>,
	 Suren Baghdasaryan <surenb@google.com>,
	Chris Li <chrisl@kernel.org>, Vernon Yang <vernon2gm@gmail.com>,
	 linux-kernel@vger.kernel.org, Qi Zheng <qi.zheng@linux.dev>,
	 Baolin Wang <baolin.wang@linux.alibaba.com>
Subject: Re: [PATCH v4 12/14] mm/vmscan: remove sc->file_taken
Date: Sun, 12 Apr 2026 18:42:03 +0800	[thread overview]
Message-ID: <adt1lU5ta_IAC3lO@KASONG-MC4> (raw)
In-Reply-To: <CAGsJ_4zpNLtx6rFFF7fG83TKZ2PpX3JyevZw0KJOL0=cv-ke1g@mail.gmail.com>

On Sat, Apr 11, 2026 at 12:43:00PM +0800, Barry Song wrote:
> On Tue, Apr 7, 2026 at 8:04 PM Kairui Song via B4 Relay
> <devnull+kasong.tencent.com@kernel.org> wrote:
> >
> > From: Kairui Song <kasong@tencent.com>
> >
> > No one is using it now, just remove it.
> >
> > Reviewed-by: Axel Rasmussen <axelrasmussen@google.com>
> > Reviewed-by: Baolin Wang <baolin.wang@linux.alibaba.com>
> > Signed-off-by: Kairui Song <kasong@tencent.com>
> 
> Can we squash this into patch 10/14, where the user of
> file_taken is removed?
> The same applies to patch 13 as well :-)

Thanks for the suggestion! They currently have different reviewed-by
and suggested-by tags and I hoped to keep the credits for other
people. Seems trivial.


  reply	other threads:[~2026-04-12 10:42 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07 11:57 [PATCH v4 00/14] mm/mglru: improve reclaim loop and dirty folio handling Kairui Song
2026-04-07 11:57 ` Kairui Song via B4 Relay
2026-04-07 11:57 ` [PATCH v4 01/14] mm/mglru: consolidate common code for retrieving evictable size Kairui Song
2026-04-07 11:57   ` Kairui Song via B4 Relay
2026-04-07 11:57 ` [PATCH v4 02/14] mm/mglru: rename variables related to aging and rotation Kairui Song
2026-04-07 11:57   ` Kairui Song via B4 Relay
2026-04-07 11:57 ` [PATCH v4 03/14] mm/mglru: relocate the LRU scan batch limit to callers Kairui Song
2026-04-07 11:57   ` Kairui Song via B4 Relay
2026-04-08  3:12   ` Chen Ridong
2026-04-07 11:57 ` [PATCH v4 04/14] mm/mglru: restructure the reclaim loop Kairui Song
2026-04-07 11:57   ` Kairui Song via B4 Relay
2026-04-08  8:08   ` Chen Ridong
2026-04-08  8:43     ` Kairui Song
2026-04-07 11:57 ` [PATCH v4 05/14] mm/mglru: scan and count the exact number of folios Kairui Song
2026-04-07 11:57   ` Kairui Song via B4 Relay
2026-04-08  8:27   ` Chen Ridong
2026-04-07 11:57 ` [PATCH v4 06/14] mm/mglru: use a smaller batch for reclaim Kairui Song
2026-04-07 11:57   ` Kairui Song via B4 Relay
2026-04-11  4:27   ` Barry Song
2026-04-07 11:57 ` [PATCH v4 07/14] mm/mglru: don't abort scan immediately right after aging Kairui Song
2026-04-07 11:57   ` Kairui Song via B4 Relay
2026-04-08  9:32   ` Chen Ridong
2026-04-07 11:57 ` [PATCH v4 08/14] mm/mglru: remove redundant swap constrained check upon isolation Kairui Song
2026-04-07 11:57   ` Kairui Song via B4 Relay
2026-04-07 11:57 ` [PATCH v4 09/14] mm/mglru: use the common routine for dirty/writeback reactivation Kairui Song
2026-04-07 11:57   ` Kairui Song via B4 Relay
2026-04-07 11:57 ` [PATCH v4 10/14] mm/mglru: simplify and improve dirty writeback handling Kairui Song
2026-04-07 11:57   ` Kairui Song via B4 Relay
2026-04-07 11:57 ` [PATCH v4 11/14] mm/mglru: remove no longer used reclaim argument for folio protection Kairui Song
2026-04-07 11:57   ` Kairui Song via B4 Relay
2026-04-07 11:57 ` [PATCH v4 12/14] mm/vmscan: remove sc->file_taken Kairui Song
2026-04-07 11:57   ` Kairui Song via B4 Relay
2026-04-11  4:43   ` Barry Song
2026-04-12 10:42     ` Kairui Song [this message]
2026-04-07 11:57 ` [PATCH v4 13/14] mm/vmscan: remove sc->unqueued_dirty Kairui Song
2026-04-07 11:57   ` Kairui Song via B4 Relay
2026-04-11  4:33   ` Barry Song
2026-04-07 11:57 ` [PATCH v4 14/14] mm/vmscan: unify writeback reclaim statistic and throttling Kairui Song
2026-04-07 11:57   ` Kairui Song via B4 Relay

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=adt1lU5ta_IAC3lO@KASONG-MC4 \
    --to=ryncsn@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=axelrasmussen@google.com \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=chenridong@huaweicloud.com \
    --cc=chrisl@kernel.org \
    --cc=david@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=kaleshsingh@google.com \
    --cc=kasong@tencent.com \
    --cc=laoar.shao@gmail.com \
    --cc=lenohou@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@kernel.org \
    --cc=qi.zheng@linux.dev \
    --cc=shakeel.butt@linux.dev \
    --cc=stevensd@google.com \
    --cc=surenb@google.com \
    --cc=vernon2gm@gmail.com \
    --cc=wangzicheng@honor.com \
    --cc=weixugc@google.com \
    --cc=yuanchu@google.com \
    --cc=yuzhao@google.com \
    --cc=zhengqi.arch@bytedance.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 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.