Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp4069709imu; Fri, 30 Nov 2018 10:25:33 -0800 (PST) X-Google-Smtp-Source: AFSGD/UdT4X7d16vgZq/GjBxR1xgAXs2cCH1iUQR4rSqz/KfMVUxiBTXkee5+xyW84X1PG4FIp1H X-Received: by 2002:a17:902:b01:: with SMTP id 1mr6786768plq.331.1543602332942; Fri, 30 Nov 2018 10:25:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543602332; cv=none; d=google.com; s=arc-20160816; b=JLGtWos8MQYC1KCKEf1MVze2r6/rHnC+fe4lt3FfYLvbGYnNF62gnjPy/2k5mc6Nyi tAGJcR5inzKMRORBITZoO52PUVjI0uAwZgs6J4hd6xRhIBTJapficFRxI9uB+Ues/R9G X+LexXSMuDdllEIfwV4UtrvNbKvrZMZ8dtVqfw6bXRsMQzrvhif8OsOWcIr9XEqYbAez bhXOqh6V+AL1n7Lh02xFVQSXPa/4Rm2EfqlfMxUk7Nh8T3pX8q9Vht27wooyeAzGFwfc tKcM70sJW6U8BKXcMFVU70LBA68+WLKkGdcwCNzQDKbx1jOF24saUXGtYakupi3r99M3 hOyw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:to:references:message-id :content-transfer-encoding:cc:date:in-reply-to:from:subject :mime-version:dkim-signature; bh=gyqSeFnxuL66/4Tb83vuNNeyna66MDa5D0/0KSnYmmA=; b=D65LiacYtu4UudSGkTf7xKdpE/ebRWvOT3VqeK2FH4u+PkgFfQjQF3oyv0K13kJ3iN a+ROmc+noF1w2DHERvtsEgx2yR1W0VUTRAYuXtFPkd9JUwOsVXNOJzIAObtXzFKycp5n ExRA0xAuZRpGXEqCWEq4ykWC3pShH1/tf5cVq9Oy8OAgv1qR00gPsf4D8rcGB5nUSx45 TWPg2mXuBzezfWufBghLL5tab8zOpmPq8BtQNw0xhs86/RugfaTsOgaD+noZO3RuZIfW G4tRLxDEUtFmtrjax0qzZKm2rzCejmrpRnNcXWOLAFQd27weUgI04od+GlnwFyBW7PLM gEhg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=Ew9SX3Rh; 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 a16si5966042plm.365.2018.11.30.10.25.17; Fri, 30 Nov 2018 10:25:32 -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; dkim=pass header.i=@linaro.org header.s=google header.b=Ew9SX3Rh; 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 S1726649AbeLAFdh (ORCPT + 99 others); Sat, 1 Dec 2018 00:33:37 -0500 Received: from mail-wm1-f66.google.com ([209.85.128.66]:34542 "EHLO mail-wm1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726127AbeLAFdh (ORCPT ); Sat, 1 Dec 2018 00:33:37 -0500 Received: by mail-wm1-f66.google.com with SMTP id y185so2234484wmd.1 for ; Fri, 30 Nov 2018 10:23:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=gyqSeFnxuL66/4Tb83vuNNeyna66MDa5D0/0KSnYmmA=; b=Ew9SX3RhnoO0FB2mWoiHH/G5G9uPbHdEEKfx28ZS1PmNH/iK+DNijjO38sGJjmcojV VTpXBHm1FHfP+HQEyVYsIQsMag6z4pGTPuHtx+kKI2peqoRPOkdUtVdfv0aFZ1MhIutc jXusQzvJpN5XrW4REVP3SAiqy/jxMo17A54Lo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=gyqSeFnxuL66/4Tb83vuNNeyna66MDa5D0/0KSnYmmA=; b=L8Q+j5Dm506t/nBHEzjW+EYReMeOwz330tXlj8yIn9T1is76ihai2+IhItC2h0HF7Q u3jNIADkV+n5cIiL3OpxIayIuzVNf5OsgwDLk2NXw0P1qxyLSyZjHkTwzaGNWzRWsyAK +tSDxD4xQF8CEAp4fTP0PO7ByYJHeoIWRcYBZBiCbqr/skggZsY42OxxUG1eqcifMUWI yIeNJkqQsImHJ2Su8+kbiVkNPdIqrunEoZWSsEJ0SdIxDaRnD9AA0AoLbY51dxAEjPDl GX4q63EIzHqXT9ETtqjJgf7O2VdbZabwGfnxGDUfgCK+8lE2eJvvzFckwgMvTqWmcogv t9dw== X-Gm-Message-State: AA+aEWaUfHxPDMe8pqcY89GxmN4uGPntEQdiLRtI1MONPc1tPl3fbWQf r9ga2X0uIyC+HM5dF+wJRT1FhQ== X-Received: by 2002:a7b:cb86:: with SMTP id m6mr6541428wmi.61.1543602206993; Fri, 30 Nov 2018 10:23:26 -0800 (PST) Received: from [192.168.0.101] (146-241-2-120.dyn.eolo.it. [146.241.2.120]) by smtp.gmail.com with ESMTPSA id z17sm5453917wrv.2.2018.11.30.10.23.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 30 Nov 2018 10:23:26 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) Subject: Re: [PATCH V2 00/10] unify the interface of the proportional-share policy in blkio/io From: Paolo Valente In-Reply-To: <25296DAE-73EC-46CC-9A98-A8B7E9017BB7@linaro.org> Date: Fri, 30 Nov 2018 19:23:24 +0100 Cc: Tejun Heo , Jens Axboe , Greg Kroah-Hartman , Li Zefan , Angelo Ruocco , Dennis Zhou , Josef Bacik , Liu Bo , Bart Van Assche , Johannes Weiner , linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, ulf.hansson@linaro.org, linus.walleij@linaro.org, broonie@kernel.org, oleksandr@natalenko.name, cgroups@vger.kernel.org, linux-doc@vger.kernel.org, Jonathan Corbet Content-Transfer-Encoding: quoted-printable Message-Id: <7D7FAB43-5F62-4402-A9B3-E7C2E30AE680@linaro.org> References: <20181119103424.3853-1-paolo.valente@linaro.org> <20181120162816.GV2509588@devbig004.ftw2.facebook.com> <25296DAE-73EC-46CC-9A98-A8B7E9017BB7@linaro.org> To: 'Paolo Valente' via bfq-iosched X-Mailer: Apple Mail (2.3445.100.39) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Il giorno 20 nov 2018, alle ore 17:50, Paolo Valente = ha scritto: >=20 >=20 >=20 >> Il giorno 20 nov 2018, alle ore 17:28, Tejun Heo ha = scritto: >>=20 >> Hello, Paolo. >>=20 >> On Mon, Nov 19, 2018 at 11:34:14AM +0100, Paolo Valente wrote: >>> - if all entities produce the same output, the this common output is >>> shown only once; >>> - if the outputs differ, then every per-entity output is shown, >>> followed by the name of the entity that produced that output. >>=20 >> So, this doesn't make sense to me. One set of numbers is meaningful, >> the other not and the user doesn't have a way to tell which one is. >> It makes no sense to present both numbers. >>=20 >=20 > I do agree that these numbers may confuse. Before discussing how to > do this better, let me tell you why we are showing them. >=20 > In the first place, the need for a diversified output showed up in the > following case. Given a group using the blkio/io controller, and two > drives > - one with legacy block and cfq > - one with blk-mq and bfq > there will be different statistics for each scheduler, for the same > interface files. >=20 > Then we understood that exactly the same happens with throttling, in > case the latter is activated on different devices w.r.t. bfq. >=20 > In addition, the same may happen, in the near future, with the > bandwidth controller Josef is working on. If the controller can be > configured per device, as with throttling, then statistics may differ, > for the same interface files, between bfq, throttling and that > controller. >=20 > More general examples could be made considering that this extension is > for the generic cgroup interface. >=20 > Of course, suggestions for a clearer way to show these numbers are > more than welcome! Maybe involved device identifiers can be somehow > gathered by the entities providing these numbers, and then shown? In > this respect, consider that, even without this extension, one still > has the fundamental problem of not knowing to which devices numbers > apply (unless I'm missing something else). >=20 Hi Tejun, have you had time to look into this? Any improvement to this interface is ok for us. We are only interested in finally solving this interface issue, as, for what concerns us directly, it has been preventing legacy code to use bfq for years. Thanks, Paolo > Thanks, > Paolo >=20 >> Thanks. >>=20 >> --=20 >> tejun >=20 > --=20 > You received this message because you are subscribed to the Google = Groups "bfq-iosched" group. > To unsubscribe from this group and stop receiving emails from it, send = an email to bfq-iosched+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout.