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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 598D2CDB46E for ; Thu, 12 Oct 2023 13:09:31 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id BABA76B014E; Thu, 12 Oct 2023 09:09:30 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id B58D86B014F; Thu, 12 Oct 2023 09:09:30 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id A20BF6B0150; Thu, 12 Oct 2023 09:09:30 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0016.hostedemail.com [216.40.44.16]) by kanga.kvack.org (Postfix) with ESMTP id 8DF146B014E for ; Thu, 12 Oct 2023 09:09:30 -0400 (EDT) Received: from smtpin10.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay06.hostedemail.com (Postfix) with ESMTP id 61D00B4FD5 for ; Thu, 12 Oct 2023 13:09:30 +0000 (UTC) X-FDA: 81336840900.10.25135E6 Received: from outbound-smtp60.blacknight.com (outbound-smtp60.blacknight.com [46.22.136.244]) by imf17.hostedemail.com (Postfix) with ESMTP id A369840014 for ; Thu, 12 Oct 2023 13:09:27 +0000 (UTC) Authentication-Results: imf17.hostedemail.com; dkim=none; spf=pass (imf17.hostedemail.com: domain of mgorman@techsingularity.net designates 46.22.136.244 as permitted sender) smtp.mailfrom=mgorman@techsingularity.net; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1697116168; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=y0WfHSGgbBNG2TWhORUZ0ekiiVJoWbQuebCHhEZCKPw=; b=E2Ja/DkIVaKUppNwgzA3r29SzZOlYDfhyrJTZesQ0c8Ch68mOLM96BAWp29iaD75u63l1+ JznSVqzCUpJYyeSTygATO4rlF+slYdo60t9grZE40XnhE1f15zpdsB09BovgIinubjA0sX TqORaOeW8Q2h9HjHOAGB1bBGfmSuMqg= ARC-Authentication-Results: i=1; imf17.hostedemail.com; dkim=none; spf=pass (imf17.hostedemail.com: domain of mgorman@techsingularity.net designates 46.22.136.244 as permitted sender) smtp.mailfrom=mgorman@techsingularity.net; dmarc=none ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1697116168; a=rsa-sha256; cv=none; b=N1FHDx2R94y0iZpoqnaadldpqd6i5IpAQBvgAw9RLs/+LiA8u10PsqaaNnFCbwPCAUnIv5 sePN1e5R5uH34wxTrBsaRylwqFGZxk9W8Gpqk3TZCx/Y0gPeDll3CbZDdcExGYwvZDA97s ufZHTa8qsAh9zwfiTc0OLlUZ4bX0tBI= Received: from mail.blacknight.com (pemlinmail05.blacknight.ie [81.17.254.26]) by outbound-smtp60.blacknight.com (Postfix) with ESMTPS id 5E6FDFB12E for ; Thu, 12 Oct 2023 14:09:24 +0100 (IST) Received: (qmail 469 invoked from network); 12 Oct 2023 13:09:24 -0000 Received: from unknown (HELO techsingularity.net) (mgorman@techsingularity.net@[84.203.197.19]) by 81.17.254.9 with ESMTPSA (AES256-SHA encrypted, authenticated); 12 Oct 2023 13:09:23 -0000 Date: Thu, 12 Oct 2023 14:09:21 +0100 From: Mel Gorman To: Andrew Morton Cc: Huang Ying , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Arjan Van De Ven , Vlastimil Babka , David Hildenbrand , Johannes Weiner , Dave Hansen , Michal Hocko , Pavel Tatashin , Matthew Wilcox , Christoph Lameter Subject: Re: [PATCH 01/10] mm, pcp: avoid to drain PCP when process exit Message-ID: <20231012130921.mkcftgq4njnpl3qy@techsingularity.net> References: <20230920061856.257597-1-ying.huang@intel.com> <20230920061856.257597-2-ying.huang@intel.com> <20231011124610.4punxroovolyvmgr@techsingularity.net> <20231011101617.2f814633defaa13e77308d9b@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <20231011101617.2f814633defaa13e77308d9b@linux-foundation.org> X-Rspamd-Queue-Id: A369840014 X-Rspam-User: X-Stat-Signature: jk3bfqriskditzr5nxwgy3runbcho3bf X-Rspamd-Server: rspam01 X-HE-Tag: 1697116167-680027 X-HE-Meta: U2FsdGVkX192SeX/ZHLLABbBSiJxlNjkpYT4Kfi+oySSuyp3VHsAUL669Da1SIFIHuD9LhH9+VoorcxV/bktyf4oD5O5TCVrv4EoQtqk8QNbJwbqWy7JlWBxUSW2EpmgOQ49U4VLEJxqFPCNGHY4/opkiRpL83MdxHvrpZhTahOu6sF9W0SFSx8Uqjtg6ulpkk8LQje7R6VV/HcQ/Qh8gvTvuz/l1J6KEW9d8XyOskDKVPs2wNK0mjBIyOhzgdjRfR47SO3mbh2Sr6kleuDQBbCYsrXxXkUuv2nKBIOHYWwkXH7ylABeMbb4qy/mL35FUbj3ze80pYoGAJdMSakcNc1mL+16zlghyji4CtTfEav1p6taWjDeCuBw2x/9vOrsGMrh4z2H4q7nTDL/t9KJ1OYbaL7BoVScG4yZxYNhbtFj5f89rGSiHaKv8u9OBgoAeKjJ8IEVQR5Pyw/EZz8xyQ/Ih95t2KuZGyxbJqlnugZ9aOtDwOQ3ZIBNXBZq67oNV+9+Dl5Qkvwu21O68RY9EBoebCD6QMOzhTkZpGu90xf5qhSsNzUvuEFYnM+fW3PP4EzxmKsxTHuw2HcWuoSAgXJ83xfD+/vqxcS2RJtQ+Xm2ZfNKpDVLKjlYoSpm/4VovsPsUt9GO0WKqly7K1Xm7NZB2oBHBjsx9h0bk0QeiwKYstm6wLU5yNu2gLiEF2lWA///rZ+rc4JP538njTSDnpl/2thOQOAmUMVTV5PAm/0ReSI17eQxk0djtYFDA6xidsSsENnHDXxQNGF9wWHZOW3vgM5v6Mbqz67EImEYne522ByyrO29vx2SmsqxCaU81VC80rBZVoivG7O4iKtYqkiyjlTqUfdh9UhuPynfONfFHWbGhVfgncAkxg6853jHDaafm6vv5yNVPtpTfMP4e9x0UuoD+dNW+Pvjfo6bQtYEdpC65vDAtApQlfSeUfcEATc7HUsiXf65UhiN95m MkOiwGIg x+2mpOgI8rwtmuP7IlNc+h56gROcARvkU9rwzNDPbPBurY+uhlNLJbmKNxEFKLNV+AiEjoag/Xy6pZHjfSB0nhe9KVMMbXdVXtGLcKKmx48uTqoKtcv7nH/fWNewANV5/xYKA46UAVGGDejW2bQ4PN6Vq8NR/nA5L4PVBKovNVttMozCaRF6zPSJuhdUzL8DmxA6udKt8giY1RBSIokomhHJwZ6Vmqk8wi3fKWO7NuGt0Nfk= 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: On Wed, Oct 11, 2023 at 10:16:17AM -0700, Andrew Morton wrote: > On Wed, 11 Oct 2023 13:46:10 +0100 Mel Gorman wrote: > > > > --- a/include/linux/mmzone.h > > > +++ b/include/linux/mmzone.h > > > @@ -676,12 +676,15 @@ enum zone_watermarks { > > > #define high_wmark_pages(z) (z->_watermark[WMARK_HIGH] + z->watermark_boost) > > > #define wmark_pages(z, i) (z->_watermark[i] + z->watermark_boost) > > > > > > +#define PCPF_PREV_FREE_HIGH_ORDER 0x01 > > > + > > > > The meaning of the flag and its intent should have been documented. > > I need to rebase mm-stable for other reasons. So let's please > decide (soon) whether Mel's review comments can be addressed > via add-on patches or whether I should drop this version of this > series altogether, during that rebase. The cache slice calculation is the only change I think may deserve a respin as it may have a material impact on the performance figures if the "size_data" value changes by too much. Huang, what do you think and how long do you think it would take to update the performance figures? As it may require multiple tests for each patch in the series, I would also be ok with a follow-on patch like "mm: page_alloc: Simply cache size estimation for PCP tuning" that documents the limitation of summing the unified caches and the impact, if any, on performance. It makes for a messy history *but* it would also record the reasons why summing hierarchies is not necessarily the best approach which also has value. I think patch 9 should be dropped as it has no impact on headline performance while adding a relatively tricky heuristic that updates within a fast path. Again, I'd like to give Huang a chance to respond and to evaluate if it materially impacts patch 10 -- I don't think it does but I didn't think very hard about it. Even if patch 9+10 had to be dropped, it would not take much from the overall value of the series. Comments and documentation alone are not grounds for pulling the series but I hope they do get addressed in follow-on patches. I think requiring them for accepting the series is unfair even if the only reason is I took too long to review. -- Mel Gorman SUSE Labs