[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120612115219.GA17348@localhost>
Date: Tue, 12 Jun 2012 19:52:19 +0800
From: Fengguang Wu <fengguang.wu@...el.com>
To: Wanpeng Li <liwp.linux@...il.com>
Cc: linux-kernel@...r.kernel.org,
Gavin Shan <shangw@...ux.vnet.ibm.com>
Subject: Re: [PATCH v2] writeback: avoid race when update bandwidth
On Tue, Jun 12, 2012 at 07:46:01PM +0800, Wanpeng Li wrote:
> From: Wanpeng Li <liwp@...ux.vnet.ibm.com>
>
> "V1 -> V2"
> * remove dirty_lock
>
> Since bdi->wb.list_lock is used to protect the b_* lists,
> so the flushers who call wb_writeback to writeback pages will
> stuck when bandwidth update policy holds this lock. In order
> to avoid this race we can introduce a new bandwidth_lock who
> is responsible for protecting bandwidth update policy.
>
> Signed-off-by: Wanpeng Li <liwp.linux@...il.com>
Applied with a new title "writeback: use a standalone lock for
updating write bandwidth". "race" is sensitive because it often
refers to some locking error.
Thank you!
Fengguang
--
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/
Powered by blists - more mailing lists