Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp6229066ybe; Tue, 17 Sep 2019 23:23:38 -0700 (PDT) X-Google-Smtp-Source: APXvYqwTeJidoQEWJvlZJKXbDf/+YnnPSMrQr3zTH0yg5fCPW//eZL0htn6+jMJcMhJXZLeNazSv X-Received: by 2002:a17:906:74d4:: with SMTP id z20mr8090854ejl.191.1568787818297; Tue, 17 Sep 2019 23:23:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568787818; cv=none; d=google.com; s=arc-20160816; b=GK5Je8J9/e4hc35kidndiiavYRv6v+xrEh6vnQzDvRiUpgIhF0UeKfV7/wsXUvyF31 v6FhApV659VtrzbNFRwjgMmYO0Vf/3BKMVwokagApH14E0mNhroqclpJs2PC/tSlz3+p kGmphuL1ERy47KnKrp1OAbAsNbItvSzcPMV3bSaWnw0C7ZWg73KSfeKboKTHfnkjtPpo PjLb5z+CNZnE3RfffCD1U9wSQ9jsy31gOBs4uPe8Qrx6VT5RBZ3ggxEgMd0xetEXYU7e DXjtwwlCvnaJRqu9fXvNx5Jy/ApDUY4qVUVr4uvYw+ZUN+tVO81P41NyoaCXRA7FEiXm 7sWQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=xTBwbLii9b70VDIiu2pkAKMCAWF61Wo+h6WzPYHryB4=; b=ix+XNyjR/q6r3veesWhlmPhgDkA9RB+JzTwQpecW4gwyCB2zhkCoW9oOgG1k70nF3T paeYGsyQgVzaAbDsuoRvnKU82zLdQLfrIGqIyqH9dHJC59wPfQuMDX6x8UwG0jwYSPP2 i79k8y8EtTUXsaOXe0mh+zCwxuHv7s7qis8+KQu+XMrPkH2vM+hCWOXM3qZ3kBQwMYV1 1CwCYxd9OXX4+39sOUG8wNJ3ZEHj7mj6ARMtkRS1/u+XfkmxHrd5tZusCQNQUkXoagTX HJ+WHBqisyu/tZi+U3jpUitm2/F1Js/bOEc8dnUZRiX3TxEjIb+Qe1hJneY54eWzWiXy 5RNg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=T+rtTKk5; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id oq6si2371228ejb.10.2019.09.17.23.23.15; Tue, 17 Sep 2019 23:23:38 -0700 (PDT) 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; dkim=pass header.i=@linaro.org header.s=google header.b=T+rtTKk5; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726663AbfIRGKV (ORCPT + 99 others); Wed, 18 Sep 2019 02:10:21 -0400 Received: from mail-ua1-f68.google.com ([209.85.222.68]:36356 "EHLO mail-ua1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726231AbfIRGKU (ORCPT ); Wed, 18 Sep 2019 02:10:20 -0400 Received: by mail-ua1-f68.google.com with SMTP id r25so1960013uam.3 for ; Tue, 17 Sep 2019 23:10:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xTBwbLii9b70VDIiu2pkAKMCAWF61Wo+h6WzPYHryB4=; b=T+rtTKk5TFAHOQsUgV/It9GsfiXKaB+bhfa5dN/sLkCoY4OmhkyktixzO9f+8YwHkk cEwMurZ/Mg+6d/IyWE/VoTFh6ibwd0Mwl6dha6HSGU+9F+3oa3E4SG8ssP4tJD2gAj2Z CgfhsGf+P+xpNd67ACMjlLHF9Vo5pLWNL+0rS9zkvOMFSZdZhpHuEdLXnjGXRBDdZa05 gMHUHQCZdMtNI95/7aMMVk9PajYLgBwdgoxrI69ssFUOuabdzO4bzrjNDV04fRzwiUtG OU6mo3S5DUmnJ0GDQ58haSoMZ17PjkKDKF6Z+zaNrgrM1JI3wMct87apJQWCU/YgECc4 x8Ew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xTBwbLii9b70VDIiu2pkAKMCAWF61Wo+h6WzPYHryB4=; b=lM+TN958O1gQUGGDLTFV8FRmWiKdMpZVS1z7BdjLMtQRWemRRqCNZr31WqUBaj73MI nbmPf05raR4kIZMztrxLJ6UBWRSeoKma9kIqUxvgHxulKpUpyXxsisFFWtgyY2/4/qeD O9H1iw3OqsqtEiqMytUMa6bzJED3rMPMEgbCVEFFPI8o0QpGxCjceoej8UDVavC7YEmp oNyY1rwU2zppm+SjzeruQDpM0lstNm+ycU9QqnekehG+MbYmPYZG4dNnDbOpEfvFeWSK jCvOuJ4+EmRT18028AcS22SafE/jcgJrUbGuL4l9KSIvgk5Lw7JoU0rq7BL0IZL+nJhE 7/2g== X-Gm-Message-State: APjAAAVfdlLRrbIGcwKXMAcGzOz/8Cm6SK0wykU57w025YF0wSmRSriX WyDPFy/2fDa0wwC9w/gIIuDa6xfHfKJwNLD83om3rA== X-Received: by 2002:ab0:1856:: with SMTP id j22mr1425618uag.19.1568787019751; Tue, 17 Sep 2019 23:10:19 -0700 (PDT) MIME-Version: 1.0 References: <20190917165148.19146-1-paolo.valente@linaro.org> <20190917165148.19146-3-paolo.valente@linaro.org> <20190917213209.GK3084169@devbig004.ftw2.facebook.com> In-Reply-To: <20190917213209.GK3084169@devbig004.ftw2.facebook.com> From: Ulf Hansson Date: Wed, 18 Sep 2019 08:09:42 +0200 Message-ID: Subject: Re: [PATCH 2/2] block, bfq: delete "bfq" prefix from cgroup filenames To: Tejun Heo , Paolo Valente Cc: Jens Axboe , linux-block , Linux Kernel Mailing List , Linus Walleij , "'Paolo Valente' via bfq-iosched" , Oleksandr Natalenko , cgroups@vger.kernel.org, Angelo Ruocco Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Tejun, Paolo, On Tue, 17 Sep 2019 at 23:32, Tejun Heo wrote: > > Hello, > > On Tue, Sep 17, 2019 at 06:51:48PM +0200, Paolo Valente wrote: > > When bfq was merged into mainline, there were two I/O schedulers that > > implemented the proportional-share policy: bfq for blk-mq and cfq for > > legacy blk. bfq's interface files in the blkio/io controller have the > > same names as cfq. But the cgroups interface doesn't allow two > > entities to use the same name for their files, so for bfq we had to > > prepend the "bfq" prefix to each of its files. However no legacy code > > uses these modified file names. This naming also causes confusion, as, > > e.g., in [1]. > > > > Now cfq has gone with legacy blk, so there is no need any longer for > > these prefixes in (the never used) bfq names. In view of this fact, this > > commit removes these prefixes, thereby enabling legacy code to truly > > use the proportional share policy in blk-mq. > > So, I wrote the iocost switching patch and don't have a strong > interest in whether bfq prefix should get dropped or not. However, I > gotta point out that flipping interface this way is way out of the > norm. > > In the previous release cycle, the right thing to do was dropping the > bfq prefix but that wasn't possible because bfq's interface wasn't > compatible at that point and didn't made to be compatible in time. Sounds like we really should send those relevant patches for stable, to set the correct ground. Then using a symlink, to make sure we don't brake current ABI, right? [...] Kind regards Uffe