From mboxrd@z Thu Jan 1 00:00:00 1970 From: Theodore Tso Subject: Re: [RFC][PATCH 5/7] writeback: use 64MB MAX_WRITEBACK_PAGES Date: Wed, 9 Sep 2009 19:29:38 -0400 Message-ID: <20090909232938.GD24951@mit.edu> References: <20090909145141.293229693@intel.com> <20090909150600.874037375@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andrew Morton , Jens Axboe , Dave Chinner , Chris Mason , Peter Zijlstra , Christoph Hellwig , jack@suse.cz, Artem Bityutskiy , LKML , linux-fsdevel@vger.kernel.org To: Wu Fengguang Return-path: Received: from thunk.org ([69.25.196.29]:51868 "EHLO thunker.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752810AbZIIXaD (ORCPT ); Wed, 9 Sep 2009 19:30:03 -0400 Content-Disposition: inline In-Reply-To: <20090909150600.874037375@intel.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, Sep 09, 2009 at 10:51:46PM +0800, Wu Fengguang wrote: > + * The maximum number of pages to writeout in a single periodic/background > + * writeback operation. 64MB means I_SYNC may be hold for up to 1 second. > + * This is not a big problem since we normally do kind of trylock on I_SYNC > + * for non-data-integrity writes. Userspace tasks doing throttled writeback > + * do not use this value. What's your justification for using 64MB? Where are you getting 1 second from? On a fast RAID array 64MB can be written in much less than 1 second. More generally, I assume your patches conflict with Jens' per-bdi patches? - Ted