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 21CDDC00140 for ; Wed, 24 Aug 2022 13:35:03 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 5B0156B0073; Wed, 24 Aug 2022 09:35:02 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 55F626B0074; Wed, 24 Aug 2022 09:35:02 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 400C1940007; Wed, 24 Aug 2022 09:35:02 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0013.hostedemail.com [216.40.44.13]) by kanga.kvack.org (Postfix) with ESMTP id 31B756B0073 for ; Wed, 24 Aug 2022 09:35:02 -0400 (EDT) Received: from smtpin27.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay05.hostedemail.com (Postfix) with ESMTP id F3A69402FB for ; Wed, 24 Aug 2022 13:35:01 +0000 (UTC) X-FDA: 79834582002.27.424DDFD Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by imf23.hostedemail.com (Postfix) with ESMTP id 0511A140042 for ; Wed, 24 Aug 2022 13:35:00 +0000 (UTC) Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out1.suse.de (Postfix) with ESMTP id B9CC022682; Wed, 24 Aug 2022 13:34:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1661348098; h=from:from:reply-to: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=cHzlnZidDyBhZ9au5VIeVEnIK4LNM13JTXYOfl1103s=; b=reifUiNBAiNnltI7FdGX+1IYGjWQOJ4KWf2m0G0+bTUxiLDd8gGVbXVQTaLYc0fczJ6FhH cfKV2AbQcp2pDjam6Aa5dhn0R8AlBcPPVM5TzKetKFb+TUB96Si9vxfBC89OC69x03VLwi uXihrwAUmT5XB1jxijKKvjijzeyDSR8= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1661348098; h=from:from:reply-to: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=cHzlnZidDyBhZ9au5VIeVEnIK4LNM13JTXYOfl1103s=; b=H3PVQyjVovuIs55Sjs+kO0ob15CCXgr/NsazWjNvgHwBLslJOTk0Hbn8gAE14hN6L6ySYB s6KDQ749KzBe/PAg== Received: from suse.de (unknown [10.163.43.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by relay2.suse.de (Postfix) with ESMTPS id 4A56A2C141; Wed, 24 Aug 2022 13:34:58 +0000 (UTC) Date: Wed, 24 Aug 2022 14:34:51 +0100 From: Mel Gorman To: Michal Hocko Cc: linux-mm@kvack.org, Christoph Hellwig , Andrew Morton , Vlastimil Babka , Johannes Weiner , LKML Subject: Re: [RFC PATCH] mm: reduce noise in show_mem for lowmem allocations Message-ID: <20220824133451.6kqttzm5t4iigz2i@suse.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1661348101; 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:dkim-signature; bh=cHzlnZidDyBhZ9au5VIeVEnIK4LNM13JTXYOfl1103s=; b=0Rmwaebbv3ymC5GmNPNGWqETjy7BSDyOxEzT90XVKKLeagWtRhTdOC1QUfBb0MDG0EjEvz OYjC8xKKVDjMPo9h+VQz2J5y0NbCMHj4Mk64f+dPxHfBGBMmSBjIOIBO6miwSdxPW6/glN ZKfZRXYIbhTPlz9+Ab5BgvZlCTwdiE4= ARC-Authentication-Results: i=1; imf23.hostedemail.com; dkim=pass header.d=suse.de header.s=susede2_rsa header.b=reifUiNB; dkim=pass header.d=suse.de header.s=susede2_ed25519 header.b=H3PVQyjV; spf=pass (imf23.hostedemail.com: domain of mgorman@suse.de designates 195.135.220.28 as permitted sender) smtp.mailfrom=mgorman@suse.de; dmarc=pass (policy=none) header.from=suse.de ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1661348101; a=rsa-sha256; cv=none; b=yO33lIavwVeMy+j+VxA5V79IL8BdoFWRerHN++b0+U95+lH6PO/EizmCIEe1KqB5I6pgrI 514WbPu8/o0F7cWFMtpl0W8K3iYXtHd2ahv3bJIlNwEHGgnchFRsOYL/ANu480XAhS6LHF UppNk4yubvBvuSpcYQeIkXPAaC8q5jE= Authentication-Results: imf23.hostedemail.com; dkim=pass header.d=suse.de header.s=susede2_rsa header.b=reifUiNB; dkim=pass header.d=suse.de header.s=susede2_ed25519 header.b=H3PVQyjV; spf=pass (imf23.hostedemail.com: domain of mgorman@suse.de designates 195.135.220.28 as permitted sender) smtp.mailfrom=mgorman@suse.de; dmarc=pass (policy=none) header.from=suse.de X-Rspam-User: X-Stat-Signature: 3yh5r96qb7g3xd89hc9iduggq5y7e4d3 X-Rspamd-Queue-Id: 0511A140042 X-Rspamd-Server: rspam10 X-HE-Tag: 1661348100-659202 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 Tue, Aug 23, 2022 at 11:22:30AM +0200, Michal Hocko wrote: > Hi, > while discussing early DMA pool pre-allocation failure with Christoph > [1] I have realized that the allocation failure warning is rather noisy > for constrained allocations like GFP_DMA{32}. Those zones are usually > not populated on all nodes very often as their memory ranges are > constrained. > > This is an attempt to reduce the ballast that doesn't provide any > relevant information for those allocation failures investigation. > Please note that I have only compile tested it (in my default config > setup) and I am throwing it mostly to see what people think about it. > > [1] http://lkml.kernel.org/r/20220817060647.1032426-1-hch@lst.de No objections. -- Mel Gorman SUSE Labs