From: Joanne Koong <joannelkoong@gmail.com>
To: miklos@szeredi.hu
Cc: linux-fsdevel@vger.kernel.org, david@redhat.com,
willy@infradead.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 0/2] fuse/mm: remove BDI_CAP_WRITEBACK_ACCT
Date: Fri, 1 Aug 2025 13:44:38 -0700 [thread overview]
Message-ID: <CAJnrk1bTNV_uUUfoP9tYjqUVM1JvWwAo1HvVARY8RXPbACHc2A@mail.gmail.com> (raw)
In-Reply-To: <20250707234606.2300149-1-joannelkoong@gmail.com>
On Mon, Jul 7, 2025 at 4:46 PM Joanne Koong <joannelkoong@gmail.com> wrote:
>
> With the changes in commit 0c58a97f919c ("fuse: remove tmp folio for
> writebacks and internal rb tree") which removed using temp folios for dirty
> page writeback, fuse can now use the default writeback accounting instead of
> doing its own accounting. This allows us to get rid of BDI_CAP_WRITEBACK_ACCT
> altogether.
>
>
> Changelog
> ---------
> v1: https://lore.kernel.org/linux-fsdevel/20250703164556.1576674-1-joannelkoong@gmail.com/
> v1 -> v2:
> * Get rid of unused variable declarations (kernel test robot)
> * Add David's acked-by
>
>
> Joanne Koong (2):
> fuse: use default writeback accounting
> mm: remove BDI_CAP_WRITEBACK_ACCT
>
> fs/fuse/file.c | 9 +-------
> fs/fuse/inode.c | 2 --
> include/linux/backing-dev.h | 14 +-----------
> mm/backing-dev.c | 2 +-
> mm/page-writeback.c | 43 ++++++++++++++++---------------------
> 5 files changed, 21 insertions(+), 49 deletions(-)
>
Hi Miklos,
Do you find this patchset acceptable for the fuse tree?
Thanks,
Joanne
> --
> 2.47.1
>
next prev parent reply other threads:[~2025-08-01 20:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 23:46 [PATCH v2 0/2] fuse/mm: remove BDI_CAP_WRITEBACK_ACCT Joanne Koong
2025-07-07 23:46 ` [PATCH v2 1/2] fuse: use default writeback accounting Joanne Koong
2025-07-09 11:06 ` Bernd Schubert
2025-07-11 11:58 ` David Hildenbrand
2025-07-07 23:46 ` [PATCH v2 2/2] mm: remove BDI_CAP_WRITEBACK_ACCT Joanne Koong
[not found] ` <CGME20250822110133eucas1p2378459d1e802c718ef6028efc06625dc@eucas1p2.samsung.com>
2025-08-22 11:01 ` Marek Szyprowski
[not found] ` <CGME20250822214238eucas1p16934a3c0a9575e6044b61e11f3635af0@eucas1p1.samsung.com>
2025-08-22 21:42 ` Marek Szyprowski
2025-08-22 23:20 ` Joanne Koong
2025-08-01 20:44 ` Joanne Koong [this message]
2025-08-18 12:28 ` [PATCH v2 0/2] fuse/mm: " Miklos Szeredi
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=CAJnrk1bTNV_uUUfoP9tYjqUVM1JvWwAo1HvVARY8RXPbACHc2A@mail.gmail.com \
--to=joannelkoong@gmail.com \
--cc=david@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=miklos@szeredi.hu \
--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;
as well as URLs for NNTP newsgroup(s).