From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from b.ns.miles-group.at ([95.130.255.144]:44724 "EHLO radon.swed.at" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752248AbdBIO4g (ORCPT ); Thu, 9 Feb 2017 09:56:36 -0500 Subject: Re: [PATCH 22/24] ubifs: Convert to separately allocated bdi To: Jan Kara References: <20170202173422.3240-1-jack@suse.cz> <20170202173422.3240-23-jack@suse.cz> <20170209121728.GE16825@quack2.suse.cz> Cc: linux-fsdevel@vger.kernel.org, Christoph Hellwig , linux-block@vger.kernel.org, Artem Bityutskiy , Adrian Hunter , linux-mtd@lists.infradead.org From: Richard Weinberger Message-ID: Date: Thu, 9 Feb 2017 15:56:29 +0100 MIME-Version: 1.0 In-Reply-To: <20170209121728.GE16825@quack2.suse.cz> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Am 09.02.2017 um 13:17 schrieb Jan Kara: >> So ->capabilities is now zero by default since you use __GFP_ZERO in >> bdi_alloc(). >> At least for UBIFS I'll add a comment on this, otherwise it is not so >> clear that UBIFS wants a BDI with no capabilities and how it achieves that. > > OK, I've modified the comment to: > > * Read-ahead will be disabled because @sb->s_bdi->ra_pages is 0. Also > * @sb->s_bdi->capabilities are initialized to 0 so there won't be any > * writeback happening. > */ Nice! Thanks, //richard