From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [RFC][PATCH 01/16] writeback: do not self-wakeup Date: Sun, 18 Jul 2010 02:44:35 -0400 Message-ID: <20100718064435.GA23811@infradead.org> References: <1279284312-2411-1-git-send-email-dedekind1@gmail.com> <1279284312-2411-2-git-send-email-dedekind1@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jens Axboe , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Artem Bityutskiy Return-path: Received: from bombadil.infradead.org ([18.85.46.34]:36299 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751750Ab0GRGoh (ORCPT ); Sun, 18 Jul 2010 02:44:37 -0400 Content-Disposition: inline In-Reply-To: <1279284312-2411-2-git-send-email-dedekind1@gmail.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, Jul 16, 2010 at 03:44:57PM +0300, Artem Bityutskiy wrote: > From: Artem Bityutskiy > > The bdi forker thread wakes up itself via 'bdi_add_to_pending()'. > And the thread is the only user of 'bdi_add_to_pending()'. Thus, > we can safely zap the unneeded 'wake_up_process()' call. At least right now it's called using call_rcu, which offloads the function to a RCU thread of some sorts.