From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.3 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0985CC07E94 for ; Fri, 4 Jun 2021 11:51:11 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 850A6613FE for ; Fri, 4 Jun 2021 11:51:10 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 850A6613FE Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=chrisdown.name Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 132776B006E; Fri, 4 Jun 2021 07:51:10 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 0E2A06B0070; Fri, 4 Jun 2021 07:51:10 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id E4FC96B0071; Fri, 4 Jun 2021 07:51:09 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0183.hostedemail.com [216.40.44.183]) by kanga.kvack.org (Postfix) with ESMTP id B51D56B006E for ; Fri, 4 Jun 2021 07:51:09 -0400 (EDT) Received: from smtpin20.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay03.hostedemail.com (Postfix) with ESMTP id 59358815A782 for ; Fri, 4 Jun 2021 11:51:09 +0000 (UTC) X-FDA: 78215875458.20.A7286AF Received: from mail-wr1-f44.google.com (mail-wr1-f44.google.com [209.85.221.44]) by imf30.hostedemail.com (Postfix) with ESMTP id 30D01E0004F2 for ; Fri, 4 Jun 2021 11:50:53 +0000 (UTC) Received: by mail-wr1-f44.google.com with SMTP id m18so9031342wrv.2 for ; Fri, 04 Jun 2021 04:51:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chrisdown.name; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=nmP5AGQDJHyblHijhBlqQ7scqZzB+IznwgL38+TeSNM=; b=ZAlxWVBtcKxrDjkMXih764aGrC3O08Yb/bplxtTlgEtkni/fyJgyzoe3B8nvwoL2kj +4EaZPbiAzOhyGJyPs+QB3gqOY/lA5qhbBXOyrYwKIV16Taqm4Qfi6/spb3pKc255DS4 rmhTOzbc725b2O8qU5ltrkbJWQRadCm5lQl60= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=nmP5AGQDJHyblHijhBlqQ7scqZzB+IznwgL38+TeSNM=; b=rFsaaHG7v2T1m4wdNRwLgH4ojsVG64zux2tUgdobL7f47tDfLIgl2IpF9ahDYTpVkR C31lY5g/rqzzI+p3H8zDmky6OSR1CM23KqIjFqxsqU0BOmm2FiKDPvT2HZ1LsFk6euzQ /EoIqif4VdCMO2WuTHNiC/zqe/h8aF2G2xQn7Squg2JsjDtUqXsyy2Bb5hWTAuer69Se 3bdBhCZ22893VWHHmlewgiX1XSIW44AXaTEWT9dxlCFMrVex0KHOGW2OuZoPxfIxbBlw v/7u7m/LyfRtZ7qjVhvEr1W2fiwK2NaQbP8NXXMYadRiKUVPM9NalmsNKCLQXMTsT9cH SWnQ== X-Gm-Message-State: AOAM533df1uXXZDAXAQIPKsChFLcilDPmOoXh3+8uR6xIEmV1H/MVidG 6DX6+NcWD5Vzfisb+jlOpBO9qw== X-Google-Smtp-Source: ABdhPJyZYMdm9ao/cla2kqJl+X6Uax9vqT0cMOWJ5115PjwBviWGzoJllV3Br2cjPFhJ8L/Dm9mRhA== X-Received: by 2002:adf:8b9a:: with SMTP id o26mr3481350wra.96.1622807461449; Fri, 04 Jun 2021 04:51:01 -0700 (PDT) Received: from localhost ([2620:10d:c093:400::5:fc89]) by smtp.gmail.com with ESMTPSA id z10sm5649645wmb.26.2021.06.04.04.51.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 04 Jun 2021 04:51:00 -0700 (PDT) Date: Fri, 4 Jun 2021 12:51:00 +0100 From: Chris Down To: yulei zhang Cc: Shakeel Butt , Tejun Heo , Zefan Li , Johannes Weiner , Christian Brauner , Cgroups , benbjiang@tencent.com, Wanpeng Li , Yulei Zhang , Linux MM , Michal Hocko , Roman Gushchin Subject: Re: [RFC 0/7] Introduce memory allocation speed throttle in memcg Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.0.7 (481f3800) (2021-05-04) X-Stat-Signature: y78xb83bsz9gubrpa8wk99gk3odxbdu9 X-Rspamd-Queue-Id: 30D01E0004F2 X-Rspamd-Server: rspam02 Authentication-Results: imf30.hostedemail.com; dkim=pass header.d=chrisdown.name header.s=google header.b=ZAlxWVBt; dmarc=pass (policy=none) header.from=chrisdown.name; spf=pass (imf30.hostedemail.com: domain of chris@chrisdown.name designates 209.85.221.44 as permitted sender) smtp.mailfrom=chris@chrisdown.name X-HE-Tag: 1622807453-65473 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: yulei zhang writes: >> Having a speed throttle is a very primitive knob: it's hard to know what the >> correct values are for a user. That's one of the reasons why we've moved away >> from that kind of tunable for blkio. >> >> Ultimately, if you want work-conserving behaviour, why not use memory.low? > >Thanks. But currently low and high are for cgroup v2 setting, do you >think we'd better >extend the same mechanism to cgroup v1? The cgroup v1 interface is frozen and in pure maintenance mode -- we're not adding new features there and haven't done so for some time. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Down Subject: Re: [RFC 0/7] Introduce memory allocation speed throttle in memcg Date: Fri, 4 Jun 2021 12:51:00 +0100 Message-ID: References: Mime-Version: 1.0 Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chrisdown.name; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=nmP5AGQDJHyblHijhBlqQ7scqZzB+IznwgL38+TeSNM=; b=ZAlxWVBtcKxrDjkMXih764aGrC3O08Yb/bplxtTlgEtkni/fyJgyzoe3B8nvwoL2kj +4EaZPbiAzOhyGJyPs+QB3gqOY/lA5qhbBXOyrYwKIV16Taqm4Qfi6/spb3pKc255DS4 rmhTOzbc725b2O8qU5ltrkbJWQRadCm5lQl60= Content-Disposition: inline In-Reply-To: List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" Content-Transfer-Encoding: 7bit To: yulei zhang Cc: Shakeel Butt , Tejun Heo , Zefan Li , Johannes Weiner , Christian Brauner , Cgroups , benbjiang-1Nz4purKYjRBDgjK7y7TUQ@public.gmane.org, Wanpeng Li , Yulei Zhang , Linux MM , Michal Hocko , Roman Gushchin yulei zhang writes: >> Having a speed throttle is a very primitive knob: it's hard to know what the >> correct values are for a user. That's one of the reasons why we've moved away >> from that kind of tunable for blkio. >> >> Ultimately, if you want work-conserving behaviour, why not use memory.low? > >Thanks. But currently low and high are for cgroup v2 setting, do you >think we'd better >extend the same mechanism to cgroup v1? The cgroup v1 interface is frozen and in pure maintenance mode -- we're not adding new features there and haven't done so for some time.