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=-13.3 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL 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 33023C47080 for ; Mon, 31 May 2021 18:21:01 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id DDAC36127C for ; Mon, 31 May 2021 18:21:00 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org DDAC36127C Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=google.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 2FC856B006C; Mon, 31 May 2021 14:21:00 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 2AC276B006E; Mon, 31 May 2021 14:21:00 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 14D436B0070; Mon, 31 May 2021 14:21:00 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0064.hostedemail.com [216.40.44.64]) by kanga.kvack.org (Postfix) with ESMTP id D923F6B006C for ; Mon, 31 May 2021 14:20:59 -0400 (EDT) Received: from smtpin33.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay02.hostedemail.com (Postfix) with ESMTP id 771DA87CC for ; Mon, 31 May 2021 18:20:59 +0000 (UTC) X-FDA: 78202342638.33.0EAA3DC Received: from mail-lf1-f42.google.com (mail-lf1-f42.google.com [209.85.167.42]) by imf22.hostedemail.com (Postfix) with ESMTP id A74F4C00CBF9 for ; Mon, 31 May 2021 18:20:47 +0000 (UTC) Received: by mail-lf1-f42.google.com with SMTP id f11so9120914lfq.4 for ; Mon, 31 May 2021 11:20:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LfVhFBreFM3+hibS+ZUYxXnl8ONhxdP+w+9OFOxmAhE=; b=YBmR9AxxYxpwcV2YLzagXsntolLPZCaQTDTHWwWzremKSRujeGHnr7cEFxCHJDPpC8 uaLyP5C8RRhr4s4wXlYMDiPX0c8RklFoJxwVY2bnKnNBvShdMuoNijcv/8zIs79d5SXC zdvUVhGtoCsnnLEyKLRSV18nJCg4OCgmpAJhGMhhMAvk0Gx5HCxFRpRoKZd1JPVFkY4B F2LjxX5mJqXCi72QGNSMJEayaBTXYrT/wmY5tLoc3DV26DQXybMi3YJZH00vfuCt6bo0 6UvsBGhqYIYVdHjwjPqABXJ7CAvie8+hqdWyqFE+u0Eu2NfkhRwAUMfTtrN4qV+1fR/n awhg== 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=LfVhFBreFM3+hibS+ZUYxXnl8ONhxdP+w+9OFOxmAhE=; b=EmClcbOjZ6b4urSl6RWClGxX/Uw+fBFspvG7H3OQMvPBGjapCCzPjgHKeLKoE7T3Lh VWTVXWRZPbz6zuD9DclwBgudKN957HmIgTFxedUvSttHUj3yT3cxpH0E6RjLCPurpWHh SG2ZYHw+4Odk6TKcmPAFP83JiOBbRY/ScbJS9FYTD8jdtx386EJ09GZaIZGULdzGQqIC LlIbZf+PKbfWPdMkZmlenfD3fNCc5vT8RcEE0iv1wpgUzYcpRlm1ZisWPY9N2dnUhUeI ffEXSusRq4m31C25x30evG79FcWwwXOQCPZbvNRQiOjDuHbKrfG+hnhGrCpwLGD3jCXi dc/g== X-Gm-Message-State: AOAM530EeXBpXV+jnUbhcoMkVUOC3YgMMyEJIUmPsYAYIlfFXmhMY3q7 u+1kCPPayKao72lVJBgDsaDz84Gk9rZV3EjdRNrEzQ== X-Google-Smtp-Source: ABdhPJx8uEnnXt5B1Cl3c0HFZ6yO2OdoHl5U2ygkG2P+Of6xFjMVbHtsr/2ctti8ISmVIYBGG9aYedzsBR4Ys8Lvxtc= X-Received: by 2002:a05:6512:2344:: with SMTP id p4mr15895230lfu.299.1622485257374; Mon, 31 May 2021 11:20:57 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Shakeel Butt Date: Mon, 31 May 2021 11:20:46 -0700 Message-ID: Subject: Re: [RFC 0/7] Introduce memory allocation speed throttle in memcg To: yulei zhang Cc: Tejun Heo , Zefan Li , Johannes Weiner , Christian Brauner , Cgroups , benbjiang@tencent.com, Wanpeng Li , Yulei Zhang , Linux MM , Michal Hocko , Roman Gushchin Content-Type: text/plain; charset="UTF-8" Authentication-Results: imf22.hostedemail.com; dkim=pass header.d=google.com header.s=20161025 header.b=YBmR9Axx; dmarc=pass (policy=reject) header.from=google.com; spf=pass (imf22.hostedemail.com: domain of shakeelb@google.com designates 209.85.167.42 as permitted sender) smtp.mailfrom=shakeelb@google.com X-Stat-Signature: ea1g3k65d861uc34swim94cazux7g6ue X-Rspamd-Queue-Id: A74F4C00CBF9 X-Rspamd-Server: rspam02 X-HE-Tag: 1622485247-292323 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000005, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Mon, May 31, 2021 at 5:11 AM yulei zhang wrote: > [...] > > Can you please explain why memory.high is not good enough for your > > use-case? You can orchestrate the memory.high limits in such a way > > that those certain cgroups hit their memory.high limit before causing > > the global reclaim. You might need to dynamically adjust the limits > > based on other workloads or unaccounted memory. > > > > Yep, dynamically adjust the memory.high limits can ease the memory pressure > and postpone the global reclaim, but it can easily trigger the oom in > the cgroups, Can you please elaborate a bit more on this? The memory.high has a strong throttling mechanism, so if you are observing memory.high being ineffective then we need to fix that. Also can you please explain a bit more on the specific of the workload which is able to escape memory.high throttling e.g. the normal number of processes/threads in the workload?