linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Andrew Morton <akpm@linux-foundation.org>,
	Hugh Dickins <hughd@google.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Yosry Ahmed <yosry.ahmed@linux.dev>,
	Nhat Pham <nphamcs@gmail.com>
Cc: Matthew Wilcox <willy@infradead.org>,
	Chengming Zhou <chengming.zhou@linux.dev>,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	linux-mm@kvack.org
Subject: stop passing a writeback_control to swap/shmem writeout v3
Date: Tue, 10 Jun 2025 07:49:36 +0200	[thread overview]
Message-ID: <20250610054959.2057526-1-hch@lst.de> (raw)

Hi all,

this series was intended to remove the last remaining users of
AOP_WRITEPAGE_ACTIVATE after my other pending patches removed the
rest, but spectacularly failed at that.

But instead it nicely improves the code, and removes two pointers
from struct writeback_control.

Changes since v2:
 - fix up kerneldoc to not leave around the documentation for a removed
   parameter
 - add back the for_reclaim removal

Changes since v1:
 - drop to patch to be merged through a different tree or later
 - fix !CONFIG_SWAP compilation

Diffstat:
 drivers/gpu/drm/i915/gem/i915_gem_shmem.c |    3 -
 drivers/gpu/drm/ttm/ttm_backup.c          |    9 ---
 fs/fuse/file.c                            |   11 ---
 fs/nfs/write.c                            |    2 
 include/linux/shmem_fs.h                  |    5 +
 include/linux/writeback.h                 |   11 ---
 include/trace/events/btrfs.h              |    7 --
 include/trace/events/writeback.h          |    8 --
 mm/page_io.c                              |   71 +++++++++++--------------
 mm/shmem.c                                |   18 ++----
 mm/swap.h                                 |    9 ++-
 mm/vmscan.c                               |   84 +++++++++++++-----------------
 mm/zswap.c                                |    5 -
 13 files changed, 96 insertions(+), 147 deletions(-)


             reply	other threads:[~2025-06-10  5:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10  5:49 Christoph Hellwig [this message]
2025-06-10  5:49 ` [PATCH 1/6] mm: split out a writeout helper from pageout Christoph Hellwig
2025-06-13  8:20   ` Baolin Wang
2025-06-10  5:49 ` [PATCH 2/6] mm: stop passing a writeback_control structure to shmem_writeout Christoph Hellwig
2025-06-13  8:31   ` Baolin Wang
2025-06-10  5:49 ` [PATCH 3/6] mm: tidy up swap_writeout Christoph Hellwig
2025-06-10  5:49 ` [PATCH 4/6] mm: stop passing a writeback_control structure to __swap_writepage Christoph Hellwig
2025-06-10 22:51   ` Nhat Pham
2025-06-10  5:49 ` [PATCH 5/6] mm: stop passing a writeback_control structure to swap_writeout Christoph Hellwig
2025-06-10  5:49 ` [PATCH 6/6] mm: remove the for_reclaim field from struct writeback_control Christoph Hellwig

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=20250610054959.2057526-1-hch@lst.de \
    --to=hch@lst.de \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=chengming.zhou@linux.dev \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=linux-mm@kvack.org \
    --cc=nphamcs@gmail.com \
    --cc=willy@infradead.org \
    --cc=yosry.ahmed@linux.dev \
    /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;
as well as URLs for NNTP newsgroup(s).