linux-kernel - Re: [PATCH 6/7] writeback: requeue_io

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111020233149.GG20542@quack.suse.cz>
Date:	Fri, 21 Oct 2011 01:31:49 +0200
From:	Jan Kara <jack@...e.cz>
To:	Wu Fengguang <fengguang.wu@...el.com>
Cc:	linux-fsdevel@...r.kernel.org, Jan Kara <jack@...e.cz>,
	Dave Chinner <david@...morbit.com>,
	Christoph Hellwig <hch@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 6/7] writeback: requeue_io_wait() on blocked inode

On Thu 20-10-11 23:22:46, Wu Fengguang wrote:
> Use requeue_io_wait() if inode is somehow blocked.
> 
> CC: Jan Kara <jack@...e.cz>
> CC: Dave Chinner <david@...morbit.com>
> Signed-off-by: Wu Fengguang <fengguang.wu@...el.com>
  Acked-by: Jan Kara <jack@...e.cz>

								Honza

> ---
>  fs/fs-writeback.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> --- linux-next.orig/fs/fs-writeback.c	2011-10-20 22:42:25.000000000 +0800
> +++ linux-next/fs/fs-writeback.c	2011-10-20 22:43:42.000000000 +0800
> @@ -471,25 +471,25 @@ writeback_single_inode(struct inode *ino
>  				/*
>  				 * slice used up: queue for next turn
>  				 */
>  				requeue_io(inode, wb);
>  			} else {
>  				/*
>  				 * Writeback blocked by something other than
>  				 * congestion. Delay the inode for some time to
>  				 * avoid spinning on the CPU (100% iowait)
>  				 * retrying writeback of the dirty page/inode
>  				 * that cannot be performed immediately.
>  				 */
> -				redirty_tail(inode, wb);
> +				requeue_io_wait(inode, wb);
>  			}
>  		} else if (inode->i_state & I_DIRTY) {
>  			/*
>  			 * Filesystems can dirty the inode during writeback
>  			 * operations, such as delayed allocation during
>  			 * submission or metadata updates after data IO
>  			 * completion.
>  			 *
>  			 * For the latter case it is very important to give
>  			 * the inode another turn on b_more_io instead of
>  			 * redirtying it.  Constantly moving dirtied_when
>  			 * forward will prevent us from ever writing out
> 
> 
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/