Received: by 2002:ac0:8c8e:0:0:0:0:0 with SMTP id r14csp45824ima; Wed, 6 Feb 2019 16:54:51 -0800 (PST) X-Google-Smtp-Source: AHgI3IZiI5jiSBqF2WH2tiVfghpubaa/1Myr4DNMT7LcychczGg33MkMN20TtLJOjFSLKMf8uDDE X-Received: by 2002:a63:f743:: with SMTP id f3mr3271139pgk.244.1549500891668; Wed, 06 Feb 2019 16:54:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549500891; cv=none; d=google.com; s=arc-20160816; b=G1SONWpACAE8BoyMyWLVbKW+B5haTdKdl7w4rvNJNWkZEoOles6pI8oqfwBfKP98xF Bc1ZY/yGfurIS4LBING79Yxg6r6XaprRYN/Q7dXUbLyKZ4xDU+So6nXj9fbQEcj6FsTS a2GTxccSnOwceJ8/JKW2xAOfMcIR64BcSLXoD3A2inWRTphN3ON8lLB/YV2Hx3VCzhrc Epu2uteds22iTHIoX/2JiJ982woFSbaOkm/CVNI3s0/4tq/MimT5SmtK8m4QLV2iT2gg swG024gI4StV8peO9Gm64wkiPYfyFyea52S2vDVNbotfcmmzjOuH56imsk7lk9qM0u6Y zryw== 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=rSwFi+axXtAVzc+v24z1Wnc76dfzMAIEWmTNZ4OPiYo=; b=ptIV8L/EwGYO2UZRBhYhB2oiCURUMKbvH8VlBg3un1KcmclPAhzk81vjPoJjz7m7O9 kb4mSMewWmGlKHQG2B0trbCJ0P6YCa5CBcvRiOS75W12LG9tVC9iJ+9LqEkeV1SiF7Ro v3JdE7p/mypxJNP8soajjVCsXL+V897KKST0cxCyKyy9iNXHSrfuwopO9koDUUyAcFAE jaEscD2iuUMp5cdPIzasNCXthseFqZbLM20Aw58mgYiqUxx0SlvcEaTmixDEfnml6Aj8 Lul0E7yhM8+JmqUxrqy15HkzkGv3mGtDYR6oKl7OFZzAvVG2ozXaojL++Q5BTljyfrur WGZw== 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 n187si4859216pfn.83.2019.02.06.16.54.35; Wed, 06 Feb 2019 16:54: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 S1726715AbfBGAx4 (ORCPT + 99 others); Wed, 6 Feb 2019 19:53:56 -0500 Received: from mx.gwdg.de ([134.76.10.20]:46075 "EHLO mx.gwdg.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725959AbfBGAx4 (ORCPT ); Wed, 6 Feb 2019 19:53:56 -0500 X-Greylist: delayed 1767 seconds by postgrey-1.27 at vger.kernel.org; Wed, 06 Feb 2019 19:53:55 EST 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 1grXUQ-0006yD-PV; Thu, 07 Feb 2019 01:24:26 +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 21667922; Thu, 07 Feb 2019 01:25:26 +0100 Received: by mailhost.tuebingen.mpg.de (sSMTP sendmail emulation); Thu, 07 Feb 2019 01:24:25 +0100 Date: Thu, 7 Feb 2019 01:24:25 +0100 From: Andre Noll To: Dave Chinner Cc: Nix , linux-bcache@vger.kernel.org, linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org, Coly Li Subject: Re: bcache on XFS: metadata I/O (dirent I/O?) not getting cached at all? Message-ID: <20190207002425.GX24140@tuebingen.mpg.de> References: <87h8dgefee.fsf@esperi.org.uk> <20190206234328.GH14116@dastard> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/T5g/TLNXpBPJeG6" Content-Disposition: inline In-Reply-To: <20190206234328.GH14116@dastard> 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 --/T5g/TLNXpBPJeG6 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 07, 10:43, Dave Chinner wrote > File data readahead: REQ_RAHEAD > Metadata readahead: REQ_META | REQ_RAHEAD >=20 > drivers/md/bcache/request.c::check_should_bypass(): >=20 > /* > * Flag for bypass if the IO is for read-ahead or background, > * unless the read-ahead request is for metadata (eg, for gfs2). > */ > if (bio->bi_opf & (REQ_RAHEAD|REQ_BACKGROUND) && > !(bio->bi_opf & REQ_PRIO)) > goto skip; >=20 > bcache needs fixing - it thinks REQ_PRIO means metadata IO. That's > wrong - REQ_META means it's metadata IO, and so this is a bcache > bug. Do you think 752f66a75abad is bad (ha!) and should be reverted? Thanks 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/ --/T5g/TLNXpBPJeG6 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQSHtF/cbZGyylvqq1Ra2jVAMQCTDwUCXFt6tgAKCRBa2jVAMQCT D6DyAKCR1mgnr+k1DigFJ3ecqGlOH6enywCggXSpPLjRVepKu8maddVQk5KMF9I= =1sEJ -----END PGP SIGNATURE----- --/T5g/TLNXpBPJeG6--