From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [PATCH 04/11] writeback: switch to per-bdi threads for
	flushing  data
Date: Fri, 29 May 2009 00:28:01 +0200
Message-ID: <20090528222801.GF11363@kernel.dk>
References: <1243511204-2328-1-git-send-email-jens.axboe@oracle.com> <1243511204-2328-5-git-send-email-jens.axboe@oracle.com> <4A1E9C13.7030406@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	tytso@mit.edu, chris.mason@oracle.com, david@fromorbit.com,
	hch@infradead.org, akpm@linux-foundation.org, jack@suse.cz,
	yanmin_zhang@linux.intel.com, richard@rsk.demon.co.uk,
	damien.wyart@free.fr
To: Artem Bityutskiy <dedekind1@gmail.com>
Return-path: <linux-kernel-owner+glk-linux-kernel-3=40m.gmane.org-S1752620AbZE1W2R@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <4A1E9C13.7030406@gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

On Thu, May 28 2009, Artem Bityutskiy wrote:
> Jens Axboe wrote:
>> +#define BDI_CAP_FLUSH_FORKER	0x00000200
>
> Would it please be possible to add a comment about
> what this flag is, and whether it is for internal
> usage or not. Not immediately obvious for me.

It's internal, probably I should just replace it with a check for
&default_backing_dev_info. If not, I'll add a comment.

-- 
Jens Axboe