Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp123788imj; Thu, 7 Feb 2019 01:28:51 -0800 (PST) X-Google-Smtp-Source: AHgI3IaBqDTB9M0NpmVGbP/T1+5h0kYFUj+lE4Idk1xzXbMif/pn65HHUz/wDN2bRNl4HuU5RzWn X-Received: by 2002:a62:cf84:: with SMTP id b126mr15047951pfg.98.1549531731231; Thu, 07 Feb 2019 01:28:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549531731; cv=none; d=google.com; s=arc-20160816; b=wl0L/m6NTuaCGE3ONSx2IkpwsFGI6pfuCnhJRJgD+56x4g9phLrwPUd49Cicsoc8M9 boOOteu6expFcGQQT4adeoc3iDFdyKm8xakOQt1nfuXD3+FAv0cJQ1M5DZ0bW/T24zns NefhkAe6Qo2O0VZb4oMdb3Gy7bwV4Vmq7oHK7PuEjEwOJ+M9N7bmr4YPRGgLIi5IoN8B w5lnsa63YoezmpEpcpWFo903IwqGchY7A89dTdWisxFPiD4ZFJkUM5MmivKklSPcon4x OG1J9Fg/nHatKVmHmiLirtjSQuEKFx6PrR/Sw0DpKm1P/CRLoim6qs3pTNKqssnP613U Hl7A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=qGMtj4Rd1ZutE9BzQgCzAu/9fo5Wk1Sx1YzRCbDIwQY=; b=ywSzFRZMb9pU8YvVwaGZBZytUNJWhwYdSZwXAqQ1f1DX7BKPWFoCzNv3D5c3WOuPMU Rfv1VFxwhlrKX00v26hz8n3T7uYjUxquP1mf6WAHlmsWfIInp5r8knlh5MIgCNCNkqrC pJ4wOXqxrH0VBxrhUuiD9Yf/0ovKFa4fxBDR0kI/xueV08bC+C9cOKDgQD43GAlw0JEn EMvCHpsdiI1o5lNm0EB48O/ucVAoJFe298ltsGUCRCSUb7W5DJM5es43vmyh4awFwadb fA8TUfuT9Jp4/+aas2zXoCbOSwKrpgrrODu3rf5G9QifAeN5+kvWwSYeWmBNNdMMOsU+ ccFg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c136si8812227pfc.141.2019.02.07.01.28.35; Thu, 07 Feb 2019 01:28:51 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726774AbfBGJ2Y (ORCPT + 99 others); Thu, 7 Feb 2019 04:28:24 -0500 Received: from mx.gwdg.de ([134.76.10.20]:45863 "EHLO mx.gwdg.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726186AbfBGJ2Y (ORCPT ); Thu, 7 Feb 2019 04:28:24 -0500 Received: from mailgw.tuebingen.mpg.de ([192.124.27.5] helo=tuebingen.mpg.de) by mailer.gwdg.de with esmtp (Exim 4.90_1) (envelope-from ) id 1grfym-0005nx-SH; Thu, 07 Feb 2019 10:28:20 +0100 Received: from [10.37.80.2] (HELO mailhost.tuebingen.mpg.de) by tuebingen.mpg.de (CommuniGate Pro SMTP 6.2.6) with SMTP id 21672203; Thu, 07 Feb 2019 10:29:20 +0100 Received: by mailhost.tuebingen.mpg.de (sSMTP sendmail emulation); Thu, 07 Feb 2019 10:28:19 +0100 Date: Thu, 7 Feb 2019 10:28:19 +0100 From: Andre Noll To: Coly Li Cc: Dave Chinner , Nix , linux-bcache@vger.kernel.org, linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org, Christoph Hellwig , axboe@kernel.dk Subject: Re: bcache on XFS: metadata I/O (dirent I/O?) not getting cached at all? Message-ID: <20190207092819.GY24140@tuebingen.mpg.de> References: <87h8dgefee.fsf@esperi.org.uk> <20190206234328.GH14116@dastard> <20190207002425.GX24140@tuebingen.mpg.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gBii9oQw/U9UOygZ" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.3 (eeed901d) (2019-02-01) X-Spam-Level: $ X-Virus-Scanned: (clean) by clamav Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --gBii9oQw/U9UOygZ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 07, 10:27, Coly Li wrote > If different file system handles metadata flags in unified ways, it is > OK to me to change the code to: !(bio->bi_opf & (REQ_META |REQ_PRIO)). Yes, that's the smallest fix that should also go into 4.19-stable. In the long run, we should try to get rid of the 45 instances of REQ_PRIO. Most users specify REQ_META | REQ_PRIO anyway, which leaves only a few other instances to look at. I think the one in submit_bh_wbc() of fs/buffer.c can just be removed while block/cfq-iosched.c does not use REQ_META at all, so the simple s/REQ_PRIO/REQ_META should be OK. drivers/staging/erofs/data.c is also easy to fix. Best Andre --=20 Max Planck Institute for Developmental Biology Max-Planck-Ring 5, 72076 T=C3=BCbingen, Germany. Phone: (+49) 7071 601 829 http://people.tuebingen.mpg.de/maan/ --gBii9oQw/U9UOygZ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQSHtF/cbZGyylvqq1Ra2jVAMQCTDwUCXFv6MAAKCRBa2jVAMQCT D5coAKCcC0GuP2KTQi/SwEAsWqfUJw6gigCfX4CU1iFd0TsxJMy93V2ZSUUPpLg= =ML1i -----END PGP SIGNATURE----- --gBii9oQw/U9UOygZ--