linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: avoid cpu lockup
Date: Mon, 17 Jul 2017 22:34:49 +0800	[thread overview]
Message-ID: <330acf45-f218-cb85-28b6-08e12c4fb888@kernel.org> (raw)
In-Reply-To: <20170716010422.GA51202@jaegeuk-macbookpro.roam.corp.google.com>

On 2017/7/16 9:04, Jaegeuk Kim wrote:
> Before retrying to flush data or dentry pages, we need to release cpu in order
> to prevent watchdog.
> 
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

Reviewed-by: Chao Yu <yuchao0@huawei.com>

> ---
> Change log from v1:
>  - timeout more specifically
> 
>  fs/f2fs/checkpoint.c | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c
> index 56bbf592e487..5b876f6d3f6b 100644
> --- a/fs/f2fs/checkpoint.c
> +++ b/fs/f2fs/checkpoint.c
> @@ -879,6 +879,7 @@ int sync_dirty_inodes(struct f2fs_sb_info *sbi, enum inode_type type)
>  	struct inode *inode;
>  	struct f2fs_inode_info *fi;
>  	bool is_dir = (type == DIR_INODE);
> +	unsigned long ino = 0;
>  
>  	trace_f2fs_sync_dirty_inodes_enter(sbi->sb, is_dir,
>  				get_pages(sbi, is_dir ?
> @@ -901,8 +902,17 @@ int sync_dirty_inodes(struct f2fs_sb_info *sbi, enum inode_type type)
>  	inode = igrab(&fi->vfs_inode);
>  	spin_unlock(&sbi->inode_lock[type]);
>  	if (inode) {
> +		unsigned long cur_ino = inode->i_ino;
> +
>  		filemap_fdatawrite(inode->i_mapping);
>  		iput(inode);
> +		/* We need to give cpu to another writers. */
> +		if (ino == cur_ino) {

We failed to flush dirty pages of inode due to encountering -EAGAIN of writepage?

Thanks,

> +			congestion_wait(BLK_RW_ASYNC, HZ/50);
> +			cond_resched();
> +		} else {
> +			ino = cur_ino;
> +		}
>  	} else {
>  		/*
>  		 * We should submit bio, since it exists several
> 

  reply	other threads:[~2017-07-17 14:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-15  1:22 [PATCH] f2fs: avoid cpu lockup Jaegeuk Kim
2017-07-16  1:04 ` [PATCH v2] " Jaegeuk Kim
2017-07-17 14:34   ` Chao Yu [this message]
2017-07-17 22:38     ` [f2fs-dev] " Jaegeuk Kim
2017-07-18  1:40       ` Chao Yu

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=330acf45-f218-cb85-28b6-08e12c4fb888@kernel.org \
    --to=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.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 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).