From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="vPYSXaRA" Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:3::133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A47FE91; Wed, 22 Nov 2023 23:02:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=In-Reply-To:Content-Type:MIME-Version :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=wGp8wkm1UDcmb84ZHwflLaHhqE+fC1a0uk/PE7zSUac=; b=vPYSXaRALrc/Uz1cQO2Sq51v8I TS2Lzn2E+ZJpBPpkCKccvCz/HQ4y3E2VDGpjaffHXmho0yEteK2TSeMDi+EY05egavpeCk9WBky9Z RYXMrzDICyh444lnHviZf9DzcZv9czI1pLQWUQ4D5Z0vYUmFqqBv0MGltYbGfdcZnYIFgFchc4j79 Ioz7b1XA5yq3bMUvWHnlK8UfqZ87JlSC+G6DZiHHlvHeuRMTR0oaxkfQYDar0OPsGphLTfFYKv3jB AAt/eK4j6kDzkt/rAhHTUhCpkF5NzkaRho1EQgiAi7azLW7Xpsasev88kZSetEb4bHcNkAXOiTNOw 0OZI+4aQ==; Received: from hch by bombadil.infradead.org with local (Exim 4.96 #2 (Red Hat Linux)) id 1r63ir-003yVI-0J; Thu, 23 Nov 2023 07:02:01 +0000 Date: Wed, 22 Nov 2023 23:02:01 -0800 From: Christoph Hellwig To: Dave Chinner Cc: Christoph Hellwig , Jan Kara , "Ritesh Harjani (IBM)" , linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: Re: [RFC 2/3] ext2: Convert ext2 regular file buffered I/O to use iomap Message-ID: References: <20231122122946.wg3jqvem6fkg3tgw@quack3> Precedence: bulk X-Mailing-List: linux-fsdevel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html On Thu, Nov 23, 2023 at 09:26:44AM +1100, Dave Chinner wrote: > I think that was me No, it was Darrick. We talkd about a lot of things, but not this :) > , as part of aligning the writeback path with > the ->iomap_valid() checks in the write path after we lock the folio > we instantiated for the write. > > It's basically the same thing - once we have a locked folio, we have > to check that the cached iomap is still valid before we use it for > anything. Yes. Currently we do that in the wb ops ->map_blocks. This can get called multiple times per folio, which is a bit silly. With the series I just posted the link to we at least stop doing that if the folio is mapped contiguously, which solves all practical cases, as the sequence check is almost free compared to the actual block mapping. For steps beyond that I'll reply to Darrick's mail.