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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D638DC4332F for ; Fri, 10 Nov 2023 22:06:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229608AbjKJWGF (ORCPT ); Fri, 10 Nov 2023 17:06:05 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49600 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229379AbjKJWGE (ORCPT ); Fri, 10 Nov 2023 17:06:04 -0500 Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 822F24229; Fri, 10 Nov 2023 14:06:01 -0800 (PST) Received: by mail-pf1-x42c.google.com with SMTP id d2e1a72fcca58-6b20577ef7bso2330781b3a.3; Fri, 10 Nov 2023 14:06:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699653961; x=1700258761; darn=vger.kernel.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:from:to:cc:subject:date:message-id :reply-to; bh=SQsMe074MamB2yzTQo6W7krdrCcJW4RDQzQCxoPsHD4=; b=g7InLcbmdDLab1Lx4iUOYFwcWf5rys/9CPVZDHc+MVA9HxZd+N/QeHGCszQqNX52vA AyUqHKWVqR4nTQGD9/jAeiiB9AmQ8ofIfxhCwFDBAdpDKMmXuDOHkicAMsX1B11aRz44 6/SDdn5J/WG4Ur7hXNtGN4ZUzS/vxFq+JEbomXPpr1fDq9wqk2eYqQbLBXJl6q6mI6SR TCfykjAvK6dKJcBtJW5xxwNQiV9yzzKMAq0QNUA3P5RSntzPPO/FajSn5YW06S6KU0gM l1Ky6N2wO5MThQe9e1c4BPdlAR7N+GyLXAn0odULZzvNKIxa6bRzkE9/+VP8A8dqWBa7 L4YA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699653961; x=1700258761; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=SQsMe074MamB2yzTQo6W7krdrCcJW4RDQzQCxoPsHD4=; b=LuzAin1TvQG6FWeWVp3t1bTGWPnO4iL4cPooR1pQKpwBffv+vlbX06L0sYraMOosy+ aalQXCubrXtkNYGtJVsIqjEy74J04Csl8CgS+C2E/HaMta2WcX3Fkqem2ADTnSi8d4DG cskTMDS3RPTL8jIPjG9AHZNJPDvWKq3kA9lL03dFxRw8VCRfJrJ4w6gFQCwiJ1zg+usX voAmsvEAiN8wRSuf6Ir80jotFVObqepAXspPG2wc1H4zSaJg0gZZq+q5iKRe4P05kDPa kEvEmjV81xRJ6543g2Kze7gITU8JYAm+hR1PrvhM3nuOSnyno3N6oq2JBmlGK7LwJBfV MO2A== X-Gm-Message-State: AOJu0YwkuFq56nYqakA1iMFtVnF3ycVSh76G9776XySEBWUcWcnZ6li4 vCAXnYOVKUGhQXPjFnYP+6M5YaedZlM= X-Google-Smtp-Source: AGHT+IGmYD+iLSGJMZ1bWcW3JwFA+GQuAkLKnNRr9ZRnrpf2Iuo4IbP+yoj9cl8CDjWN8FMq3eC3SA== X-Received: by 2002:a05:6a21:7746:b0:181:a3ae:115b with SMTP id bc6-20020a056a21774600b00181a3ae115bmr438823pzc.61.1699653960858; Fri, 10 Nov 2023 14:06:00 -0800 (PST) Received: from localhost ([2620:10d:c090:400::4:7384]) by smtp.gmail.com with ESMTPSA id fm26-20020a056a002f9a00b0068620bee456sm180253pfb.209.2023.11.10.14.06.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 10 Nov 2023 14:06:00 -0800 (PST) Sender: Tejun Heo Date: Fri, 10 Nov 2023 12:05:59 -1000 From: "tj@kernel.org" To: John Groves Cc: Gregory Price , "linux-kernel@vger.kernel.org" , "linux-cxl@vger.kernel.org" , "linux-mm@kvack.org" , "cgroups@vger.kernel.org" , "linux-doc@vger.kernel.org" , "ying.huang@intel.com" , "akpm@linux-foundation.org" , "mhocko@kernel.org" , "lizefan.x@bytedance.com" , "hannes@cmpxchg.org" , "corbet@lwn.net" , "roman.gushchin@linux.dev" , "shakeelb@google.com" , "muchun.song@linux.dev" , Gregory Price , "jgroves@micron.com" Subject: Re: [RFC PATCH v4 0/3] memcg weighted interleave mempolicy control Message-ID: References: <20231109002517.106829-1-gregory.price@memverge.com> <0100018bb64636ef-9daaf0c0-813c-4209-94e4-96ba6854f554-000000@email.amazonses.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0100018bb64636ef-9daaf0c0-813c-4209-94e4-96ba6854f554-000000@email.amazonses.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, On Thu, Nov 09, 2023 at 10:48:56PM +0000, John Groves wrote: > This approach checks all the important boxes: it only applies to apps where > it's enabled, the weighting can vary from one app to another, the > kernel is not affected, and the numa topology is not buried. Can't it be a mempol property which is inherited by child processes? Then all you'll need is e.g. adding systemd support to configure this at service unit level. I'm having a bit of hard time seeing why this needs to be a cgroup feature when it doesn't involve dynamic resource accounting / enforcement at all. Thanks. -- tejun