From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-dy1-f193.google.com (mail-dy1-f193.google.com [74.125.82.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 47A7632C95B for ; Thu, 12 Feb 2026 21:25:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=74.125.82.193 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770931531; cv=none; b=TEgZ8RcSnoWo88H5ChcyyfdpIXT4HlXRa2f2CCWxi/zkxURgt7WNYxOi3Vk1/X2umbaT/THaAsuSZoFPhfZkt73XPEdINMulWPp46g/clY6jf/kmozumAQseK+6Oa0bBOn0GMxzEsbR0Iy+3ot38HOmVnkGEvfeuDsYmsNVho9o= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770931531; c=relaxed/simple; bh=4VOKf0xEU2BdqyQq8g7jnYrqEcpcWaBqoYKpXVHd/0s=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=erRjkU3LuLb5Pp62U+cNz+6nJV+GXUv57nTb4JJDX+ll7UHDlm8NdVmxrTzVwqEKIHRzjDlUMAGeLKIgBN/vsQ6uUNlc+12dH1T7Xw6sKf3Vib787O1HUGqz9KYW6Sf7HGFoqMHSJ9o9pKalTiKbWUfvdbUB+Pk0+AEa73evwfc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=TfGm4oPC; arc=none smtp.client-ip=74.125.82.193 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="TfGm4oPC" Received: by mail-dy1-f193.google.com with SMTP id 5a478bee46e88-2ba94dbf739so335435eec.1 for ; Thu, 12 Feb 2026 13:25:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1770931529; x=1771536329; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=BCh0D1PgFCAnFv/ObCs8wiM+Hp+1ve3byqWcWmOrNFg=; b=TfGm4oPCraS7qYkj0oMlo5ClFTiXNU7zFYJqg6K25lKKfwNx4Mf0sVKc1qpLapH3v3 iS9CkbCthQZXOsdqJGUfZNZWv0ygM2G94LTBuHhwyl74Xzs7S7/z674qFezw8lGVh0Sx 3m52Hd5f0DuVr+4RE+JylZyHDOwpjJSjh7iG0Wew180LvOcnYUyc/BeIVswsruGN6tc5 lv2W9hYdoB0cUGPqLV+2AYO3CdvTOMaxPW5EVnAzqF9pUnh5a/xgC4XK+e9AW44E2u+s kxiE7UYhKH2t1aseUJPKKw608Dw53yfvQzWqR8vJweVqiglae19ukWUKY/FvcsEJj28x hZzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1770931529; x=1771536329; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=BCh0D1PgFCAnFv/ObCs8wiM+Hp+1ve3byqWcWmOrNFg=; b=WMAgoqgOUwkSi4H6+uDQEjrM1Gsb3P71ZiQAMsIo2sUKWS1r/uUWwCrgAuu8vUsVT2 xgvh1TG8AmiCuz3LEpQMYT8sx1PYFysSSYLFlVtSt9rlswClY6KbzHVywcZ+xvV4EDVB 6Y5JMc05Da8/UOpJCEtFnbsFKVCeb3vV3lZ1pv9ASfyMMBloUtM+rbib/uobjw/Kre+Z vJLLPn+67b0MXU6115bJF8C5xCEJ/rqmnvvctEAFTR0HGaHa1/Fcu+05rLYt5Cy0TXXa nchm7WHqqmUNSBXekxbpaJhnGhigTqFmovSxCF6P2xuAY0CkcmejrUIh0jzgbVoo/nOF siJg== X-Forwarded-Encrypted: i=1; AJvYcCUUE0scGoaSaKEuGuqgO5rv/ut52AUs1PLzTaTT2/yUWQ2YADdQm20iKpL78iUmIPizbNFUCZZFRsGvcDI=@vger.kernel.org X-Gm-Message-State: AOJu0YyXCkYNY1wZPvvF/ZjYulhyPlDmlEfghbaqRuCVfG2LWclsUQVM 43ykN+UVL6yzG4iMIzcaJTRHJ8Z+WQchTNf9gxm2fV+DDF3AxHMRdwyk X-Gm-Gg: AZuq6aJGppt5V9yrAvamGS7638yEa0BBECD5LPf+BL+GGfn23aWbqzkpAjZXXe9wS8B KtPHY2ecMgA0Lg7HezG4Sp+xw7lUWIAt7UwmysWCHgPcSrq1LdtYn611DjFohXcMRVd7uBdkE2l lwa2SMYHvDRJaGYl226+GpEzfEM8tTLZnyy8+DcL1ytqLy/6iSNu7V8IyheaWz+jUfOl40EEvWl 0iu0inHHNWXo/xqgcrslS0z6C+LuiK4mrdcIrQ//nh+EDWecTNSIhVTjz+kkOuq9aAFzu3ue3eF luJ8nD6wRxXLpNq0tEkzGpP0R/Dh/YDQ2FLrHeFu2mZKdiXiBrLiyYtE48vYSuCCgBj3JTaIX0M I3ubPkX/kTX3S0a9io6nlhHRPlJM1m4qKAsVvtxplhFYLDj0TN/x36KSnDhmyLnLfdTnEKqsBpw ujvU5A7fz6FZoFIBiUVx5cFSxueud8Mxhd X-Received: by 2002:a05:7301:7c12:b0:2b7:f44a:a6ad with SMTP id 5a478bee46e88-2baba136a9cmr114756eec.42.1770931529389; Thu, 12 Feb 2026 13:25:29 -0800 (PST) Received: from [192.168.4.196] ([73.222.117.172]) by smtp.gmail.com with ESMTPSA id 5a478bee46e88-2ba9dcd0614sm4779914eec.22.2026.02.12.13.25.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 12 Feb 2026 13:25:28 -0800 (PST) Message-ID: Date: Thu, 12 Feb 2026 13:25:26 -0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 1/2] mm/mempolicy: track page allocations per mempolicy To: Vlastimil Babka , linux-mm@kvack.org Cc: apopple@nvidia.com, akpm@linux-foundation.org, axelrasmussen@google.com, byungchul@sk.com, cgroups@vger.kernel.org, david@kernel.org, eperezma@redhat.com, gourry@gourry.net, jasowang@redhat.com, hannes@cmpxchg.org, joshua.hahnjy@gmail.com, Liam.Howlett@oracle.com, linux-kernel@vger.kernel.org, lorenzo.stoakes@oracle.com, matthew.brost@intel.com, mst@redhat.com, mhocko@suse.com, rppt@kernel.org, muchun.song@linux.dev, zhengqi.arch@bytedance.com, rakie.kim@sk.com, roman.gushchin@linux.dev, shakeel.butt@linux.dev, surenb@google.com, virtualization@lists.linux.dev, weixugc@google.com, xuanzhuo@linux.alibaba.com, ying.huang@linux.alibaba.com, yuanchu@google.com, ziy@nvidia.com, kernel-team@meta.com References: <20260212045109.255391-1-inwardvessel@gmail.com> <20260212045109.255391-2-inwardvessel@gmail.com> <96b63efb-551f-4dd5-b4a2-ac67da577431@suse.cz> Content-Language: en-US From: JP Kobryn In-Reply-To: <96b63efb-551f-4dd5-b4a2-ac67da577431@suse.cz> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 2/12/26 7:24 AM, Vlastimil Babka wrote: > On 2/12/26 05:51, JP Kobryn wrote: >> It would be useful to see a breakdown of allocations to understand which >> NUMA policies are driving them. For example, when investigating memory >> pressure, having policy-specific counts could show that allocations were >> bound to the affected node (via MPOL_BIND). >> >> Add per-policy page allocation counters as new node stat items. These >> counters can provide correlation between a mempolicy and pressure on a >> given node. >> >> Signed-off-by: JP Kobryn >> Suggested-by: Johannes Weiner > > Are the numa_{hit,miss,etc.} counters insufficient? Could they be extended > in a way that would capture any missing important details? A counter per > policy type seems exhaustive, but then on one hand it might be not important > to distinguish beetween some of them, and on the other hand it doesn't track > the nodemask anyway. The two patches of the series should complement each other. When investigating memory pressure, we could identify the affected nodes (patch 2). Then we can cross-reference the policy-specific stats to find any correlation (this patch). I think extending numa_* counters would call for more permutations to account for the numa stat per policy. I think distinguishing between MPOL_DEFAULT and MPOL_BIND is meaningful, for example. Am I understanding your question?