All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiubo Li <xiubli@redhat.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: idryomov@gmail.com, ceph-devel@vger.kernel.org
Subject: Re: [PATCH] ceph: don't implement writepage
Date: Tue, 7 Jun 2022 20:43:19 +0800	[thread overview]
Message-ID: <de924b6d-fc2f-175f-fc23-6ad04071a5b0@redhat.com> (raw)
In-Reply-To: <20220607112703.17997-1-jlayton@kernel.org>


On 6/7/22 7:27 PM, Jeff Layton wrote:
> Remove ceph_writepage as it's not strictly required these days.
>
> To quote from commit 21b4ee7029c9 (xfs: drop ->writepage completely):
>
>      ->writepage is only used in one place - single page writeback from
>      memory reclaim. We only allow such writeback from kswapd, not from
>      direct memory reclaim, and so it is rarely used. When it comes from
>      kswapd, it is effectively random dirty page shoot-down, which is
>      horrible for IO patterns. We will already have background writeback
>      trying to clean all the dirty pages in memory as efficiently as
>      possible, so having kswapd interrupt our well formed IO stream only
>      slows things down. So get rid of xfs_vm_writepage() completely.
>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
> ---
>   fs/ceph/addr.c | 25 -------------------------
>   1 file changed, 25 deletions(-)
>
> diff --git a/fs/ceph/addr.c b/fs/ceph/addr.c
> index 40830cb9b599..3489444c55b9 100644
> --- a/fs/ceph/addr.c
> +++ b/fs/ceph/addr.c
> @@ -680,30 +680,6 @@ static int writepage_nounlock(struct page *page, struct writeback_control *wbc)
>   	return err;
>   }
>   
> -static int ceph_writepage(struct page *page, struct writeback_control *wbc)
> -{
> -	int err;
> -	struct inode *inode = page->mapping->host;
> -	BUG_ON(!inode);
> -	ihold(inode);
> -
> -	if (wbc->sync_mode == WB_SYNC_NONE &&
> -	    ceph_inode_to_client(inode)->write_congested)
> -		return AOP_WRITEPAGE_ACTIVATE;
> -
> -	wait_on_page_fscache(page);
> -
> -	err = writepage_nounlock(page, wbc);
> -	if (err == -ERESTARTSYS) {
> -		/* direct memory reclaimer was killed by SIGKILL. return 0
> -		 * to prevent caller from setting mapping/page error */
> -		err = 0;
> -	}
> -	unlock_page(page);
> -	iput(inode);
> -	return err;
> -}
> -
>   /*
>    * async writeback completion handler.
>    *
> @@ -1394,7 +1370,6 @@ static int ceph_write_end(struct file *file, struct address_space *mapping,
>   const struct address_space_operations ceph_aops = {
>   	.readpage = netfs_readpage,
>   	.readahead = netfs_readahead,
> -	.writepage = ceph_writepage,
>   	.writepages = ceph_writepages_start,
>   	.write_begin = ceph_write_begin,
>   	.write_end = ceph_write_end,

Sounds reasonable.

Will merge it into the testing branch.

Thanks Jeff!

-- Xiubo



  reply	other threads:[~2022-06-07 12:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 11:27 [PATCH] ceph: don't implement writepage Jeff Layton
2022-06-07 12:43 ` Xiubo Li [this message]
2022-06-07 16:41 ` Luís Henriques
2022-06-08  6:37 ` Christoph Hellwig
2022-06-08 10:19   ` Jeff Layton
2022-06-08 12:37     ` Xiubo Li

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=de924b6d-fc2f-175f-fc23-6ad04071a5b0@redhat.com \
    --to=xiubli@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=idryomov@gmail.com \
    --cc=jlayton@kernel.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 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.