linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	Carlos Maiolino <cem@kernel.org>,
	willy@infradead.org, dlemoal@kernel.org, hans.holmberg@wdc.com,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-xfs@vger.kernel.org
Subject: Re: allow file systems to increase the minimum writeback chunk size v2
Date: Wed, 22 Oct 2025 11:38:25 -0700	[thread overview]
Message-ID: <20251022113825.f9d0a2f3143929f9e1f2967d@linux-foundation.org> (raw)
In-Reply-To: <20251022053434.GA3729@lst.de>

On Wed, 22 Oct 2025 07:34:34 +0200 Christoph Hellwig <hch@lst.de> wrote:

> Looks like everything is reviewed now, can we get this queued up
> as it fixes nasty fragmentation for zoned XFS?
> 
> It seems like the most recent writeback updates went through the VFS
> tree, although -mm has been quite common as well.

mpage, writeback, readahead, filemap, buffer.c  etc have traditionally
been MM tree things (heck, I basically wrote them all a mere 20 years
ago).

They're transitioning to being fs things nowadays, and that makes sense
- filesystems are the clients for this code.

But please do keep cc'ing linux-mm and myself on this work.

> >  fs/fs-writeback.c         |   26 +++++++++-----------------
> >  fs/super.c                |    1 +
> >  fs/xfs/xfs_zone_alloc.c   |   28 ++++++++++++++++++++++++++--
> >  include/linux/fs.h        |    1 +
> >  include/linux/writeback.h |    5 +++++

VFS tree, please.


  reply	other threads:[~2025-10-22 18:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17  3:45 Christoph Hellwig
2025-10-17  3:45 ` [PATCH 1/3] writeback: cleanup writeback_chunk_size Christoph Hellwig
2025-10-17 12:31   ` Jan Kara
2025-10-20  9:35   ` Jan Kara
2025-10-24 14:11   ` Nirjhar Roy (IBM)
2025-10-17  3:45 ` [PATCH 2/3] writeback: allow the file system to override MIN_WRITEBACK_PAGES Christoph Hellwig
2025-10-17 12:32   ` Jan Kara
2025-10-17 15:45   ` Darrick J. Wong
2025-10-20  9:35   ` Jan Kara
2025-10-24 14:33   ` Nirjhar Roy (IBM)
2025-10-24 15:12     ` Christoph Hellwig
2025-10-17  3:45 ` [PATCH 3/3] xfs: set s_min_writeback_pages for zoned file systems Christoph Hellwig
2025-10-22  5:34 ` allow file systems to increase the minimum writeback chunk size v2 Christoph Hellwig
2025-10-22 18:38   ` Andrew Morton [this message]
2025-10-29 14:55 ` Christian Brauner
2025-10-29 14:56 ` Christian Brauner

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=20251022113825.f9d0a2f3143929f9e1f2967d@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=cem@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=hans.holmberg@wdc.com \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-xfs@vger.kernel.org \
    --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