Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp429156ybv; Thu, 20 Feb 2020 00:54:20 -0800 (PST) X-Google-Smtp-Source: APXvYqyTLIz2hh5Msica1+4CLQDYYui/jKyda7l45S2vm/AjSxy99QEpiTAbgtKjuF6KV+6YsLJ8 X-Received: by 2002:a05:6830:1014:: with SMTP id a20mr9303181otp.302.1582188859451; Thu, 20 Feb 2020 00:54:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1582188859; cv=none; d=google.com; s=arc-20160816; b=DuQkq5kKXJLvmk6yE29oM96mFGXtOoQwxW+pa35mNq0TYgVS7fbFT8XDPhRigMggC9 qNugIf09xOVYR+z9GH40cxAJt1HqKbsHiU5dFkBsOWV2En3dvVtmVmXQ861cERQEjsO9 BcWKC+TfpeaYNcYdu4sTBaQvpnB3PbsgWUWxdRCrHZR94MT0eAg8BYnafMoafYZhIxW4 TxWMRW0gWFEl/LxybrS0tM6E0HCIvB5zNJF+AOIo33fny60Coy/KrTr950cVpEDWrgix GduWjk8jBpOvBAU5llBap/7F1G7cH8SqOTNrmx0GLr8uTDVSvDAkrIxZyUYrHTKjRxmE 6ZrA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=aG3Ei0HHrgrm5hahSqfhzECWrrr1Sfgr3ScUKH/KTBA=; b=KJC6DJSaa0sc/t4N2OmICq6N+U6S9V4HKSz+P8GAfKi7hWt23O1AFwvbsytuNlBckK fHmucineoPRUY7onVBcSu6b5rJs85Lv3xtdkg5L8e+oxEiFdo4M3pCXE+4uHaI/8iKwB 7E3zj2ubEAJWoZ1wATlG27px/lNAfLDf3UNtWy0m0RgCweBAAe7kAd3oypgrWxUFgXya pylWKnHYBBNdpOYzENJLAutlQRcsjK3dpJ5/V5w6j4qVCxykipPdzS5JBf1YPDF9git7 Rz2Wq+Z4/zC66ObA9kd6S+jQVbubpxn4PinJWI1QPcn+/EhVRi2dRKfNC8g9SvVm0cnI +FRg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@yandex-team.ru header.s=default header.b=DMtrzoek; 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=yandex-team.ru Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x2si1385131otk.29.2020.02.20.00.54.04; Thu, 20 Feb 2020 00:54:19 -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=@yandex-team.ru header.s=default header.b=DMtrzoek; 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=yandex-team.ru Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726813AbgBTIwr (ORCPT + 99 others); Thu, 20 Feb 2020 03:52:47 -0500 Received: from forwardcorp1p.mail.yandex.net ([77.88.29.217]:43866 "EHLO forwardcorp1p.mail.yandex.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726501AbgBTIwr (ORCPT ); Thu, 20 Feb 2020 03:52:47 -0500 Received: from mxbackcorp1o.mail.yandex.net (mxbackcorp1o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::301]) by forwardcorp1p.mail.yandex.net (Yandex) with ESMTP id 788632E148B; Thu, 20 Feb 2020 11:52:44 +0300 (MSK) Received: from vla1-5a8b76e65344.qloud-c.yandex.net (vla1-5a8b76e65344.qloud-c.yandex.net [2a02:6b8:c0d:3183:0:640:5a8b:76e6]) by mxbackcorp1o.mail.yandex.net (mxbackcorp/Yandex) with ESMTP id moNltwzpYg-qhLOh1HB; Thu, 20 Feb 2020 11:52:44 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex-team.ru; s=default; t=1582188764; bh=aG3Ei0HHrgrm5hahSqfhzECWrrr1Sfgr3ScUKH/KTBA=; h=In-Reply-To:Message-ID:From:Date:References:To:Subject:Cc; b=DMtrzoek+TmVbTa6j2DbONx0J+k79QrdkWNyMyV/0sJKcJppkPl2lCC3ecUFzsZYV b4hrr8Sf5vN3p2xJyA1xY+YxSViH21C5E+HOXnvmpfVyNQtC51bo1wl0sUpksXW4ga jrAUTseUglLkNENA9nvhf8/k8QqFaHdfP09YPiuI= Authentication-Results: mxbackcorp1o.mail.yandex.net; dkim=pass header.i=@yandex-team.ru Received: from dynamic-red.dhcp.yndx.net (dynamic-red.dhcp.yndx.net [2a02:6b8:0:40c:8448:fbcc:1dac:c863]) by vla1-5a8b76e65344.qloud-c.yandex.net (smtpcorp/Yandex) with ESMTPSA id swC0L2TyHI-qh1C4eZD; Thu, 20 Feb 2020 11:52:43 +0300 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client certificate not present) Subject: Re: [PATCH v2] sched/fair: add burst to cgroup cpu bandwidth controller To: Dave Chiluk , Ben Segall Cc: Peter Zijlstra , cgroups@vger.kernel.org, Linux Kernel Mailing List , Juri Lelli , Vincent Guittot , Steven Rostedt , Ingo Molnar , Mel Gorman , Cong Wang , Dietmar Eggemann References: <157476581065.5793.4518979877345136813.stgit@buzz> From: Konstantin Khlebnikov Message-ID: <98998672-4fab-2bb2-5f2d-fd6d83025036@yandex-team.ru> Date: Thu, 20 Feb 2020 11:52:43 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-CA Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 17/02/2020 22.56, Dave Chiluk wrote: > On Fri, Feb 14, 2020 at 12:55 PM wrote: >> I'm not sure that starting with full burst runtime is best, though it >> definitely seems likely to be one of those things where sometimes it's >> what you want and sometimes it's not. > > We (Indeed) definitely want to start with a full burst bank in most > cases, as this would help with slow/throttled start-up times for our > Jitted and interpreter-based language applications. I agree that it > would be nice to have it be configurable. > > Dave. > fyi. Unfortunately, this e-mail may be temporarily turned off for the > next few weeks, I apologize in advance for any bounced messages to me. > How much burst time you are planning to use? On our side common setup should be like this: cpu.cfs_period_us = 100ms cpu.cfs_quota_us = 100ms * X cpu.cfs_burst_us = clamp(400ms * X, 100ms, 100ms * NR_CPUS) Where is X is a cpu power in cpus.