linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	chris.mason@oracle.com, hch@infradead.org, tytso@mit.edu,
	akpm@linux-foundation.org, jack@suse.cz,
	trond.myklebust@fys.uio.no
Subject: Re: [PATCH 5/7] writeback: inline allocation failure handling in bdi_alloc_queue_work()
Date: Mon, 14 Sep 2009 15:13:42 +0200	[thread overview]
Message-ID: <20090914131342.GI24075@duck.suse.cz> (raw)
In-Reply-To: <1252920994-11141-6-git-send-email-jens.axboe@oracle.com>

On Mon 14-09-09 11:36:32, Jens Axboe wrote:
> This gets rid of work == NULL in bdi_queue_work() and puts the
> OOM handling where it belongs.
  Looks good.

Acked-by: Jan Kara <jack@suse.cz>

								Honza
> 
> Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
> ---
>  fs/fs-writeback.c |   55 +++++++++++++++++++++++++++-------------------------
>  1 files changed, 29 insertions(+), 26 deletions(-)
> 
> diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
> index d7592c7..5cd8b3b 100644
> --- a/fs/fs-writeback.c
> +++ b/fs/fs-writeback.c
> @@ -139,21 +139,19 @@ static void wb_clear_pending(struct bdi_writeback *wb, struct bdi_work *work)
>  
>  static void bdi_queue_work(struct backing_dev_info *bdi, struct bdi_work *work)
>  {
> -	if (work) {
> -		work->seen = bdi->wb_mask;
> -		BUG_ON(!work->seen);
> -		atomic_set(&work->pending, bdi->wb_cnt);
> -		BUG_ON(!bdi->wb_cnt);
> +	work->seen = bdi->wb_mask;
> +	BUG_ON(!work->seen);
> +	atomic_set(&work->pending, bdi->wb_cnt);
> +	BUG_ON(!bdi->wb_cnt);
>  
> -		/*
> -		 * Make sure stores are seen before it appears on the list
> -		 */
> -		smp_mb();
> +	/*
> +	 * Make sure stores are seen before it appears on the list
> +	 */
> +	smp_mb();
>  
> -		spin_lock(&bdi->wb_lock);
> -		list_add_tail_rcu(&work->list, &bdi->work_list);
> -		spin_unlock(&bdi->wb_lock);
> -	}
> +	spin_lock(&bdi->wb_lock);
> +	list_add_tail_rcu(&work->list, &bdi->work_list);
> +	spin_unlock(&bdi->wb_lock);
>  
>  	/*
>  	 * If the default thread isn't there, make sure we add it. When
> @@ -165,14 +163,12 @@ static void bdi_queue_work(struct backing_dev_info *bdi, struct bdi_work *work)
>  		struct bdi_writeback *wb = &bdi->wb;
>  
>  		/*
> -		 * If we failed allocating the bdi work item, wake up the wb
> -		 * thread always. As a safety precaution, it'll flush out
> -		 * everything
> +		 * End work now if this wb has no dirty IO pending. Otherwise
> +		 * wakeup the handling thread
>  		 */
> -		if (!wb_has_dirty_io(wb)) {
> -			if (work)
> -				wb_clear_pending(wb, work);
> -		} else if (wb->task)
> +		if (!wb_has_dirty_io(wb))
> +			wb_clear_pending(wb, work);
> +		else if (wb->task)
>  			wake_up_process(wb->task);
>  	}
>  }
> @@ -192,11 +188,20 @@ static void bdi_alloc_queue_work(struct backing_dev_info *bdi,
>  {
>  	struct bdi_work *work;
>  
> +	/*
> +	 * This is WB_SYNC_NONE writeback, so if allocation fails just
> +	 * wakeup the thread for old dirty data writeback
> +	 */
>  	work = kmalloc(sizeof(*work), GFP_ATOMIC);
> -	if (work)
> +	if (work) {
>  		bdi_work_init(work, wbc);
> +		bdi_queue_work(bdi, work);
> +	} else {
> +		struct bdi_writeback *wb = &bdi->wb;
>  
> -	bdi_queue_work(bdi, work);
> +		if (wb->task)
> +			wake_up_process(wb->task);
> +	}
>  }
>  
>  void bdi_start_writeback(struct writeback_control *wbc)
> @@ -852,10 +857,8 @@ static void bdi_writeback_all(struct writeback_control *wbc)
>  	rcu_read_lock();
>  
>  	list_for_each_entry(bdi, &bdi_list, bdi_list) {
> -		if (!bdi_has_dirty_io(bdi))
> -			continue;
> -
> -		bdi_alloc_queue_work(bdi, wbc);
> +		if (bdi_has_dirty_io(bdi))
> +			bdi_alloc_queue_work(bdi, wbc);
>  	}
>  
>  	rcu_read_unlock();
> -- 
> 1.6.4.1.207.g68ea
> 
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2009-09-14 13:13 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14  9:36 [PATCH 0/7] Post merge per-bdi writeback patches v2 Jens Axboe
2009-09-14  9:36 ` [PATCH 1/7] writeback: merely wakeup flusher thread if work allocation fails for WB_SYNC_NONE Jens Axboe
2009-09-14 12:34   ` Jan Kara
2009-09-14 12:39     ` Jens Axboe
2009-09-14 13:19       ` Christoph Hellwig
2009-09-14  9:36 ` [PATCH 2/7] Assign bdi in super_block Jens Axboe
2009-09-14 13:02   ` Jan Kara
2009-09-14 18:25     ` Trond Myklebust
2009-09-14 18:36       ` Jens Axboe
2009-09-15 10:14         ` Jan Kara
2009-09-15 10:22           ` Jens Axboe
2009-09-15 13:16           ` Trond Myklebust
2009-09-14  9:36 ` [PATCH 3/7] writeback: only use bdi_writeback_all() for WB_SYNC_NONE writeout Jens Axboe
2009-09-14 13:12   ` Jan Kara
2009-09-14  9:36 ` [PATCH 4/7] writeback: use RCU to protect bdi_list Jens Axboe
2009-09-14 11:10   ` Minchan Kim
2009-09-14 11:11     ` Jens Axboe
2009-09-14  9:36 ` [PATCH 5/7] writeback: inline allocation failure handling in bdi_alloc_queue_work() Jens Axboe
2009-09-14 13:13   ` Jan Kara [this message]
2009-09-14  9:36 ` [PATCH 6/7] writeback: separate starting of sync vs opportunistic writeback Jens Axboe
2009-09-14 13:33   ` Jan Kara
2009-09-14 13:42     ` Christoph Hellwig
2009-09-14 19:28       ` Jens Axboe
2009-09-14 19:42         ` Jens Axboe
2009-09-15  9:08           ` Jan Kara
2009-09-15  9:14             ` Jens Axboe
2009-09-15 11:44               ` Jens Axboe
2009-09-15 12:58                 ` Jan Kara
2009-09-15 13:04                   ` Jens Axboe
2009-09-15 13:08                     ` Christoph Hellwig
2009-09-15 13:17                       ` Jens Axboe
2009-09-15 14:01                       ` Jan Kara
2009-09-15 14:09                         ` Chris Mason
2009-09-14  9:36 ` [PATCH 7/7] writeback: splice dirty inode entries to default bdi on bdi_destroy() Jens Axboe
2009-09-14 10:56   ` Jens Axboe

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=20090914131342.GI24075@duck.suse.cz \
    --to=jack@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=chris.mason@oracle.com \
    --cc=hch@infradead.org \
    --cc=jens.axboe@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    --cc=tytso@mit.edu \
    /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).