Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp5635996pxb; Tue, 16 Feb 2021 03:53:31 -0800 (PST) X-Google-Smtp-Source: ABdhPJxlF6Rn65elcvLJW0XOBHhLl1OEKKXuKsxQCuTSxA68zcmjA1pTrCh8FF5+B7VmMV2pMEmH X-Received: by 2002:a17:906:d8b5:: with SMTP id qc21mr19345339ejb.62.1613476411465; Tue, 16 Feb 2021 03:53:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1613476411; cv=none; d=google.com; s=arc-20160816; b=dunk3UK7Q6g07tId67eMNe2cpq1DoGWn4N/YE59WE52IddPda0gz6EIG527owvBCi8 A3jRhVeUChN8HbNHRILvrY2rGcvpLTHRXH7pHofgcioWZtCZGcCfljmQIUgO/a6DTnXy wGELxrS1qp5V+MPoglLcd+Isf6HXmGvkV62dMhAlQLS/UKwOjN+K1MK+FocqkPtZk0vV Vv19puq98jmFv9rlioyGNEdnQXKkhV7tVXfYdeV2Hm/8OuEAwwsLUV41QOlCaJN8Ezo+ JSCVOOIhA6VZX8fb52K0qhqd9OvUcOKmROy45WUB7kGdc62+QE6wiL8Qz0qdFFrD9wzE ShGw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:date:content-id:mime-version:subject :cc:to:references:in-reply-to:from:organization:dkim-signature; bh=coH4C7xdrmgBE3/XsHGmHJNC7rb47IS/kJchI+NLx3A=; b=sOp1kJ+wjqjnnNWzoJWB2itA7gOxnF9gLzSVAEhjh+lPvPiJcHjq/bOfKUEifgoD8b k4k3W1UAh+3dg2iH+yvGzZqmPA/dP6Ryd7MvJpMCqwFuAvXGKy26JH1hPi59RlpqUVa1 jEN6Lf7B12iGKrYV9beisjw10zz6PX1RO6urZ3kicNJeokmFNgunoULNyOLQnh8C+F02 d/KmgSERD8vFkmbCpEm9S6z2/7Cj/d5xvTnedFiwHfx/kL69p1oESg8CmAuMd/rgmfY6 2/vsAbrs3pFKfoZop5jXvqp0OfVP9BhrzvnQM+mUItxscH7k/dPlh9waoo7uq/TxAf// /54A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=f0h4L9wh; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id si1si2219902ejb.294.2021.02.16.03.53.02; Tue, 16 Feb 2021 03:53:31 -0800 (PST) Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=f0h4L9wh; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230268AbhBPLwE (ORCPT + 99 others); Tue, 16 Feb 2021 06:52:04 -0500 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:47944 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230243AbhBPLuD (ORCPT ); Tue, 16 Feb 2021 06:50:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1613476117; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=coH4C7xdrmgBE3/XsHGmHJNC7rb47IS/kJchI+NLx3A=; b=f0h4L9whb9+3Km2kw3JhRy6CWrPQP+7i17e7XYH8vh3Io7fUAjgNClD+Zv4JhABwBSZq33 BgTI4iiP73jtKA0rDyzRMxBnrNOoXt8Z0yZxUpD3WCYVwxoPi5uOWZlGrd7f4PmRe6Pn1i e4duNyQl1zpyHhLy5NnXpDrmaL5sB6Q= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-349-jKcmJhrLMwullgSDWVKkPg-1; Tue, 16 Feb 2021 06:48:35 -0500 X-MC-Unique: jKcmJhrLMwullgSDWVKkPg-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id B44BE801977; Tue, 16 Feb 2021 11:48:32 +0000 (UTC) Received: from warthog.procyon.org.uk (ovpn-119-68.rdu2.redhat.com [10.10.119.68]) by smtp.corp.redhat.com (Postfix) with ESMTP id EDB605C1B4; Tue, 16 Feb 2021 11:48:24 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <20210216103215.GB27714@lst.de> References: <20210216103215.GB27714@lst.de> <161340385320.1303470.2392622971006879777.stgit@warthog.procyon.org.uk> <161340389201.1303470.14353807284546854878.stgit@warthog.procyon.org.uk> To: Christoph Hellwig , "Matthew Wilcox (Oracle)" Cc: dhowells@redhat.com, Trond Myklebust , Anna Schumaker , Steve French , Dominique Martinet , Alexander Viro , linux-mm@kvack.org, linux-cachefs@redhat.com, linux-afs@lists.infradead.org, linux-nfs@vger.kernel.org, linux-cifs@vger.kernel.org, ceph-devel@vger.kernel.org, v9fs-developer@lists.sourceforge.net, linux-fsdevel@vger.kernel.org, Jeff Layton , David Wysochanski , linux-kernel@vger.kernel.org Subject: Re: [PATCH 03/33] mm: Implement readahead_control pageset expansion MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1429174.1613476104.1@warthog.procyon.org.uk> Date: Tue, 16 Feb 2021 11:48:24 +0000 Message-ID: <1429175.1613476104@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org Christoph Hellwig wrote: > On Mon, Feb 15, 2021 at 03:44:52PM +0000, David Howells wrote: > > Provide a function, readahead_expand(), that expands the set of pages > > specified by a readahead_control object to encompass a revised area with a > > proposed size and length. > ... > So looking at linux-next this seems to have a user, but that user is > dead wood given that nothing implements ->expand_readahead. Interesting question. Code on my fscache-iter branch does implement this, but I was asked to split the patchset up, so that's not in this subset. > Looking at the code structure I think netfs_readahead and > netfs_rreq_expand is a complete mess and needs to be turned upside > down, that is instead of calling back from netfs_readahead to the > calling file system, split it into a few helpers called by the > caller. > > But even after this can't we just expose the cache granule boundary > to the VM so that the read-ahead request gets setup correctly from > the very beginning? You need to argue this one with Willy. In my opinion, the VM should ask the filesystem and the expansion be done before ->readahead() is called. Willy disagrees, however. David