Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp818690ybt; Wed, 1 Jul 2020 10:45:04 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwkUW8kvGVxP1PJtrU9nGZGSGiVBlEyoPU55quWUrmx5PIehOYi7x4w82OAlLaJ5EsSIEkn X-Received: by 2002:a50:b964:: with SMTP id m91mr31818911ede.37.1593625504641; Wed, 01 Jul 2020 10:45:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593625504; cv=none; d=google.com; s=arc-20160816; b=NPT85osow45qgOIX2HxCwZAUF6Sa0bnuiaonM/1qyLZu9zEoG1AojEeiOvrU9HAiVo XVQkAZjmZk1AtfIOLTkWRJo/YpoZLydluIGhxzqi7KE9shUkzzWCDeixddNxPVFl+TRl vnqdqW8wWOogSXEI0pIHODvK7IDx4ngOLOwskcTHyaekKN6Byfmeoq4Bw1ik/ynqNTfv QDLPXge/9eJ80cKREudSMyKmUrd1i09CDM7Ye+kp59dEXkOJZCakNdjZHriUSnNt/MsS lnVy4hhnm+YuIKzRuTakRDyvjAhKb1UHNrDBmo/nd6rYwXuf4wO3bDg4Tb8k+ep6fNIu zu3Q== 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:dkim-signature; bh=wobg33Jd/mLzwVfLH+qw23dgCxhuXQvI8VYke7pyLt8=; b=eMP6FgBTaZQe5IT6QoJBsLg+9z1glt0zgfeo2Uwi531EdjdsGdc7tAH/TLnzkYHUBL mmoCGi0WYDUfEHzkzbcac/8+ec38pPxF1b18pZ93Hb6hZXwsbNeC4xZsZ+TZHVEl6EX9 jirJmFsLDuZg31raJQARiwScR462XaHj18ooAhthyXJ6hjB+5K+qXqBXhO2HmURqlYjm ebdNjjmveIxRXnaUYx3eT4UAypzYK/IFmYG2UH8Fu6i0VDu6LZnM53LdOKqCANno7tPU 4DlJ9RBInNOvliqoRT55aSZYbCWJU9vdbsDKAsK/x8v2ryFijzGPQAcURm+LNM71ynV8 +eHg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=PRzGm0c1; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-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 i25si4297653edr.503.2020.07.01.10.44.41; Wed, 01 Jul 2020 10:45:04 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-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=PRzGm0c1; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-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 S1732773AbgGARmb (ORCPT + 99 others); Wed, 1 Jul 2020 13:42:31 -0400 Received: from us-smtp-2.mimecast.com ([207.211.31.81]:42222 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1729871AbgGARmb (ORCPT ); Wed, 1 Jul 2020 13:42:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1593625350; 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=wobg33Jd/mLzwVfLH+qw23dgCxhuXQvI8VYke7pyLt8=; b=PRzGm0c1rXHn/qNPwxz/BOJMt7y0gIewcLkBsWBqyFh+ZhrfeT4OdmF/uqhRBsVkWONTXs WFtWmz2gCvv/yKDpLSnvO3j9WDn3F88E3QTb3vYEnYzKPzLaX549IFdRzjL4W3KVU02zv6 ewD8hmWoWOegpYL1OkU8S+scBAy/RDw= 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-237-kaM7C-6POYeJEkH2MyXrxA-1; Wed, 01 Jul 2020 13:42:28 -0400 X-MC-Unique: kaM7C-6POYeJEkH2MyXrxA-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id C53871940920; Wed, 1 Jul 2020 17:42:26 +0000 (UTC) Received: from localhost (unknown [10.18.25.174]) by smtp.corp.redhat.com (Postfix) with ESMTPS id B13D379220; Wed, 1 Jul 2020 17:42:23 +0000 (UTC) Date: Wed, 1 Jul 2020 12:41:03 -0400 From: Mike Snitzer To: Christoph Hellwig Cc: Jens Axboe , linux-raid@vger.kernel.org, linux-mm@kvack.org, linux-bcache@vger.kernel.org, linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, drbd-dev@tron.linbit.com, dm-devel@redhat.com, Tejun Heo , cgroups@vger.kernel.org, linux-btrfs@vger.kernel.org Subject: Re: remove dead bdi congestion leftovers Message-ID: <20200701164103.GC27063@redhat.com> References: <20200701090622.3354860-1-hch@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200701090622.3354860-1-hch@lst.de> User-Agent: Mutt/1.5.21 (2010-09-15) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 01 2020 at 5:06am -0400, Christoph Hellwig wrote: > Hi Jens, > > we have a lot of bdi congestion related code that is left around without > any use. This series removes it in preparation of sorting out the bdi > lifetime rules properly. I could do some git archeology to see what the fs, mm and block core changes were to stop using bdi congested but a pointer to associated changes (or quick recap) would save me some time. Also, curious to know how back-pressure should be felt back up the IO stack now? (apologies if these are well worn topics, I haven't been tracking this area of development). Thanks, Mike