Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp4165147imu; Tue, 18 Dec 2018 10:03:54 -0800 (PST) X-Google-Smtp-Source: AFSGD/V48gHIHxqB46pE712lO3g/s9o7a1R8Z3zamzCfAlW8nMc77dIEd8uHVfZnoZUDFtDW0hOw X-Received: by 2002:a63:d208:: with SMTP id a8mr16326061pgg.77.1545156234626; Tue, 18 Dec 2018 10:03:54 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1545156234; cv=none; d=google.com; s=arc-20160816; b=jHS4OnKsOHDDq4Hcaya2AgcI2zJC2TFcOFmvHBFOTPLvfGMdqMYH61qiGv/kVTamIj biXfsEmnD4DOdBXZbzt0fXedjQIC5P3ftAOZA/qrtqR1xZGH53X2nwDunmDH9w/tV7Dm 2mmM4nAhPU1K5EXuXGlzPLe5fYPDH8hTgoXhU30krxcGzQu5wOoXqnvUbUg2MFTId0xC I812amgvfrCgBa7MpCbKVs2Gm+2RpDHSmDsMCwAmqe+WjINFRiwmscy+bCC0hDA+EBUV +wdefW6v5tJs6LoGRpVtD4S33Ho0IaLZ+FWYD24a/qkwX0QkHyCXF8hPGl/b21lHDgkq Cqrw== 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=Qxr/PEmJFsRrEklCc2G+CWcsbCOLd3hDZQ0GvBRgCew=; b=m02aLZWBj3G1xLk89tcU3hrPlX1RoYe2l0X7hjVCtIlzbfwnpOIfxK1qVOONFnIk9Z iJqR1BGuTXiS0vpIpYwd9N2Venm6dpsnIz+3SHv8IXcD6m8ILMFdhC2sl3UjGgu1nybT 0d4Rp2aw9D3v0Ob7ikx3egCsEFjbVhe8WQBvqnV8SOPJfvjzDMdu5ziwpOiahKvQDEko WfGVhasqbg7FDazGQPcs7FE9lBz6IGX3S1SRFb9auB0QL3gi+Ndze+f8R6eaKpuVJufO udr+/SS7ohN/ErS1yHCGilBJDQQpOqjJuxoLIAKtxS4Ahrex0UT/JFRzx/G/jYVs6WW2 cnCg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=pvDaeC2c; 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=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p5si5971567pls.338.2018.12.18.10.03.37; Tue, 18 Dec 2018 10:03:54 -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=fail header.i=@gmail.com header.s=20161025 header.b=pvDaeC2c; 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=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727547AbeLRQld (ORCPT + 99 others); Tue, 18 Dec 2018 11:41:33 -0500 Received: from mail-yb1-f196.google.com ([209.85.219.196]:41097 "EHLO mail-yb1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727529AbeLRQla (ORCPT ); Tue, 18 Dec 2018 11:41:30 -0500 Received: by mail-yb1-f196.google.com with SMTP id e124so6701759ybb.8; Tue, 18 Dec 2018 08:41:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Qxr/PEmJFsRrEklCc2G+CWcsbCOLd3hDZQ0GvBRgCew=; b=pvDaeC2cbDIqoVcA3a91jug0vWkjNpchLP/2I2Se4eWplDu/fuTKeXSS/VJV8ywV1q i9aIGZnHhCRXA6OCtBTff+pbjuA3yI/AmyteGwyk/ELfIMyGyjOd0u5u8a5SOEmS9IyO loJmL9R+FyAQmPEtz4V0PzR8dCuRwlkIpRyVKvJREujIeYdchZnzile8RH0l1A6BZpRI j68L6pqFN65vlqESWiDbK4M/bnJifR3Gc5TIrP1uASGG+6OO85l6m1TH3ogYBiDfjiyS V34/ZTwVwcy9A7pkAhG8JbqhOMNOXb7TEejxdnWjRpFX3IqFfOhMCPYq56irF+sNyjFe wQow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=Qxr/PEmJFsRrEklCc2G+CWcsbCOLd3hDZQ0GvBRgCew=; b=U6rzVB3Ub3haAzvsHdsrHVSv+vcUqGYBoTD5Qnr+eRphwWtY1pnlzSEnGUyR1FNNme kPKcXrO54YkxnzsGrywufaLgDkVxMIKLeBBGUWNmHRjme0Jz6KFaPTt85uOEB8efp2CW ed5ugY8A0kADJVUYKrkkBaQR9/D4uQV9o6nXlotS2JQSmRrgQUDS3BSUR90nEqsdR67x U3MOkxlJiogJ/l2Vp46ENJ1vQ1nxNDEpmGvPe+Gyjr//jmjG+76KHc8QgYmD3MT+lsj+ 9lKHju18oyzxE1hQehDN38kEoLBUMusBl+6al2GrI6BWNsSwjL2doyfJqSJXXBJvSgwl IacQ== X-Gm-Message-State: AA+aEWaNsV8pCJgDNlZPdbaChex4lBESPoCfndXYqEXOZIrjSzdtf1w1 xe7VdKEYK2ERfWZGnymlPqU= X-Received: by 2002:a5b:3d1:: with SMTP id t17mr17820633ybp.435.1545151288729; Tue, 18 Dec 2018 08:41:28 -0800 (PST) Received: from localhost ([2620:10d:c091:200::6:e01b]) by smtp.gmail.com with ESMTPSA id y83sm5015892ywd.65.2018.12.18.08.41.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Dec 2018 08:41:27 -0800 (PST) Date: Tue, 18 Dec 2018 08:41:26 -0800 From: Tejun Heo To: Paolo Valente Cc: Angelo Ruocco , 'Paolo Valente' via bfq-iosched , 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 Subject: Re: [PATCH V2 00/10] unify the interface of the proportional-share policy in blkio/io Message-ID: <20181218164126.GX2509588@devbig004.ftw2.facebook.com> References: <20181119103424.3853-1-paolo.valente@linaro.org> <20181120162816.GV2509588@devbig004.ftw2.facebook.com> <25296DAE-73EC-46CC-9A98-A8B7E9017BB7@linaro.org> <7D7FAB43-5F62-4402-A9B3-E7C2E30AE680@linaro.org> <20181130184256.GI2509588@devbig004.ftw2.facebook.com> <5534B7D4-A5D9-4F44-9620-970A7F9EC140@linaro.org> <874A0232-2103-4364-BD88-F33B85D6A764@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <874A0232-2103-4364-BD88-F33B85D6A764@linaro.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, Paolo. On Tue, Dec 18, 2018 at 08:48:10AM +0100, Paolo Valente wrote: > If Tejun cannot see any solution to his concern, then can we just > switch to this extension, considering that > - for non-shared names the interface is *identical* to the current > one; > - by using this new interface, and getting feedback we could > understand how to better handle Tejun's concern? > A lot of systems do use weights, and people don't even know that these > systems don't work correctly in blk-mq. And they won't work correctly > in any available configuration from 4.21, if we don't fix this problem. So, when seen from userland, how it should behave isn't vague or complicated. For a given device and policy type, there can be only one implementation active. It doesn't make sense to have two weight mechanisms active on one device, right? So, the interface should only present what makes sense to the user for both configuration knobs and statistics, and that'd be a hard requirement because we don't want to present confusing spurious information to userspace. There seemd to have been significant misunderstandings as to what the requirements are when this was discussed way back, so idk what the good path forward is at this point. Just keep the current names? Thanks. -- tejun