From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Christoph Hellwig <hch@lst.de>,
Bob Peterson <rpeterso@redhat.com>,
Andreas Gruenbacher <agruenba@redhat.com>,
"Darrick J. Wong" <djwong@kernel.org>,
Naohiro Aota <naohiro.aota@wdc.com>
Cc: Johannes Thumshirn <jth@kernel.org>,
cluster-devel@redhat.com, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 3/4] zonefs: remove ->writepage
Date: Mon, 11 Jul 2022 13:47:50 +0900 [thread overview]
Message-ID: <3b411188-50ec-4844-73c3-afed8dd3fcf2@opensource.wdc.com> (raw)
In-Reply-To: <20220711041459.1062583-4-hch@lst.de>
On 7/11/22 13:14, Christoph Hellwig wrote:
> ->writepage is only used for single page writeback from memory reclaim,
> and not called at all for cgroup writeback. Follow the lead of XFS
> and remove ->writepage and rely entirely on ->writepages.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> fs/zonefs/super.c | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/fs/zonefs/super.c b/fs/zonefs/super.c
> index 053299758deb9..062c3f1da0327 100644
> --- a/fs/zonefs/super.c
> +++ b/fs/zonefs/super.c
> @@ -232,13 +232,6 @@ static const struct iomap_writeback_ops zonefs_writeback_ops = {
> .map_blocks = zonefs_write_map_blocks,
> };
>
> -static int zonefs_writepage(struct page *page, struct writeback_control *wbc)
> -{
> - struct iomap_writepage_ctx wpc = { };
> -
> - return iomap_writepage(page, wbc, &wpc, &zonefs_writeback_ops);
> -}
> -
> static int zonefs_writepages(struct address_space *mapping,
> struct writeback_control *wbc)
> {
> @@ -266,7 +259,6 @@ static int zonefs_swap_activate(struct swap_info_struct *sis,
> static const struct address_space_operations zonefs_file_aops = {
> .read_folio = zonefs_read_folio,
> .readahead = zonefs_readahead,
> - .writepage = zonefs_writepage,
> .writepages = zonefs_writepages,
> .dirty_folio = filemap_dirty_folio,
> .release_folio = iomap_release_folio,
Acked-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2022-07-11 4:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 4:14 remove iomap_writepage Christoph Hellwig
2022-07-11 4:14 ` [PATCH 1/4] gfs2: stop using generic_writepages in gfs2_ail1_start_one Christoph Hellwig
2022-07-11 10:27 ` Andreas Gruenbacher
2022-07-11 14:30 ` Christoph Hellwig
2022-07-11 4:14 ` [PATCH 2/4] gfs2: remove ->writepage Christoph Hellwig
2022-07-11 23:22 ` Andreas Grünbacher
2022-07-12 4:57 ` Christoph Hellwig
2022-07-11 4:14 ` [PATCH 3/4] zonefs: " Christoph Hellwig
2022-07-11 4:47 ` Damien Le Moal [this message]
2022-07-11 9:12 ` Johannes Thumshirn
2022-07-11 4:14 ` [PATCH 4/4] iomap: remove iomap_writepage Christoph Hellwig
2022-07-11 4:48 ` Damien Le Moal
-- strict thread matches above, loose matches on Subject: below --
2022-07-19 4:13 remove iomap_writepage v2 Christoph Hellwig
2022-07-19 4:13 ` [PATCH 3/4] zonefs: remove ->writepage Christoph Hellwig
2022-07-19 6:56 ` Chaitanya Kulkarni
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=3b411188-50ec-4844-73c3-afed8dd3fcf2@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=agruenba@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=jth@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=naohiro.aota@wdc.com \
--cc=rpeterso@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox