Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id A4299C6379F for ; Thu, 23 Feb 2023 17:31:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229989AbjBWRbF (ORCPT ); Thu, 23 Feb 2023 12:31:05 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49456 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229536AbjBWRbD (ORCPT ); Thu, 23 Feb 2023 12:31:03 -0500 Received: from out-45.mta1.migadu.com (out-45.mta1.migadu.com [IPv6:2001:41d0:203:375::2d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 63B90570B7 for ; Thu, 23 Feb 2023 09:31:01 -0800 (PST) Date: Thu, 23 Feb 2023 09:30:53 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1677173458; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=1WZIJ8pUmzgqf8s+eBJbOZDw0S7cY6i0ZgBo0K3FG/Q=; b=pioTvFJu7T1+T4/dTxeZZqfGM2/TWjnxl4BbSskW/8iJMEnf3xGmnYpO2bJERJoSDtrpit 0eku3xR9czaZIWNvA8YRjTXPDh9dCUtqB9XDSEDs0pibvBl25q+K8xrv85ULglmXpU5SYL spx63rP8+9iIRtqUhMP6lWjWqydHSU0= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Roman Gushchin To: Matthew Chae Cc: Michal =?iso-8859-1?Q?Koutn=FD?= , Johannes Weiner , Michal Hocko , Shakeel Butt , Andrew Morton , kernel , Christopher Wong , Muchun Song , "cgroups@vger.kernel.org" , "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] mm/memcontrol: add memory.peak in cgroup root Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Migadu-Flow: FLOW_OUT Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 23, 2023 at 04:22:33PM +0000, Matthew Chae wrote: > Hi Michal, > > First off, thank you for sharing your opinion. > I'd like to monitor the peak memory usage recorded of overall system or at least cgroup accounted memory through memory.peak. > But it looks like this is not relevant to what I wanted. > It might be good to have some proper way for checking the system's peak memory usage recorded. I guess you might want to do the opposite: instead of tracking the peak usage, you can record the bottom of available free memory. Thanks!