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 46D87C46467 for ; Wed, 11 Jan 2023 15:36:08 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 8D1068E0003; Wed, 11 Jan 2023 10:36:07 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 859288E0001; Wed, 11 Jan 2023 10:36:07 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 6FA588E0003; Wed, 11 Jan 2023 10:36:07 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0015.hostedemail.com [216.40.44.15]) by kanga.kvack.org (Postfix) with ESMTP id 595558E0001 for ; Wed, 11 Jan 2023 10:36:07 -0500 (EST) Received: from smtpin21.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay04.hostedemail.com (Postfix) with ESMTP id 23F0E1A0649 for ; Wed, 11 Jan 2023 15:36:07 +0000 (UTC) X-FDA: 80342919174.21.8FE6F9A Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by imf16.hostedemail.com (Postfix) with ESMTP id 68113180016 for ; Wed, 11 Jan 2023 15:36:04 +0000 (UTC) Authentication-Results: imf16.hostedemail.com; dkim=pass header.d=suse.com header.s=susede1 header.b=LBbLmLMO; dmarc=pass (policy=quarantine) header.from=suse.com; spf=pass (imf16.hostedemail.com: domain of mhocko@suse.com designates 195.135.220.29 as permitted sender) smtp.mailfrom=mhocko@suse.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1673451364; 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=nRH21KYwjUTBDhGKpPMV5E370DEd1Sm0RKzqrNyyp7k=; b=cmnNcpTqYMpnnc7OCPE6QJY/Vd/0Q5Tm0xPJD7/YOfZ3KUGWP7lpYUfh5j9LcHEYu0H3HV c83X2vh2H5KgR4YSaaP7xnRKgZdGbBa6yxrBwHFMH49tAGSEbnw9PQUeX0xvdt17oBpC8h nEKkfbEqMzOV5RbdFWiXYKZfMW4+uI0= ARC-Authentication-Results: i=1; imf16.hostedemail.com; dkim=pass header.d=suse.com header.s=susede1 header.b=LBbLmLMO; dmarc=pass (policy=quarantine) header.from=suse.com; spf=pass (imf16.hostedemail.com: domain of mhocko@suse.com designates 195.135.220.29 as permitted sender) smtp.mailfrom=mhocko@suse.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1673451364; a=rsa-sha256; cv=none; b=zLzBQaB/FmbP2CQRBsOYh3k0nRh1HdZtcKODqxrvB7RDgtTA+pM1CLKdhYPbGAxfPeiUJp HN8nSJsjgb5NZjM38hT4Yp48UFC7x99KP0IYVeHt3RYta78YeJCpT9SS8iFD18op4uZHQa d75I6WLC3Dmbe0M05HmBsren+NnRjjs= Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id A58544C9F; Wed, 11 Jan 2023 15:36:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1673451362; 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=nRH21KYwjUTBDhGKpPMV5E370DEd1Sm0RKzqrNyyp7k=; b=LBbLmLMOPkJcUSIZBVyYh9fnucdZiPquR9gDpo20B4LC97zeqTL3kZdEp5WNo7NK9zWm1U J0qc2+/QjMOdTTRKHmRw3JeY7uMa9w1AVMtpq9lrN25SYUi4QU37/SMM2VaUk3gxpwHw+3 jLyAMD/CkOp40WbWNC8/1rHcCB9YTWI= Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 876D11358A; Wed, 11 Jan 2023 15:36:02 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id 9I4qHmLXvmNfNwAAMHmgww (envelope-from ); Wed, 11 Jan 2023 15:36:02 +0000 Date: Wed, 11 Jan 2023 16:36:01 +0100 From: Michal Hocko To: Mel Gorman Cc: Linux-MM , Andrew Morton , NeilBrown , Thierry Reding , Matthew Wilcox , Vlastimil Babka , LKML Subject: Re: [PATCH 3/7] mm/page_alloc: Explicitly record high-order atomic allocations in alloc_flags Message-ID: References: <20230109151631.24923-1-mgorman@techsingularity.net> <20230109151631.24923-4-mgorman@techsingularity.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230109151631.24923-4-mgorman@techsingularity.net> X-Rspamd-Queue-Id: 68113180016 X-Rspamd-Server: rspam09 X-Rspam-User: X-Stat-Signature: 3rf7xo13r6n8mifjiffuzbjiadnq7jdq X-HE-Tag: 1673451364-557621 X-HE-Meta: U2FsdGVkX1/WuLsULZu2DHNMWHFfUjYTXJ+r2uRg4VEXM6A8ncmz1BELumd7e6LON9AKb3dR6UilIudn0B5n2BI3CxoDTW8ytorCGdVsNasZdjPeL5x9g2UvurH84ZTaNPA+mxq0HSQQhI2aV4szY+Bqs2Yj45onlpgOxqsqk4i/9d043ZHHh1mXKta/cAFh504UJZ7ZwhQX7SYAotwZPIu6uXtCeFKFVwlZX/8KC/QyUzrNUJ72I5vx+SOEFq2p5D7b8UaFaAzOpEu99B7CTwvb9FhiwOnkV2gEfKDzPG8MPVv1cSaf2eHhFP4qLlUrV2DP3gqonHJOqtNfPzBS6eRMtTJd4/H+qIJZv/itH325oNwTM9gHiTOLGJkDvBIQt6A+6OdVgA8SDDqtcQCTI9sYHErpS0M0l+/6PNlCG82Frb5MbkT8Un8mc6P47RfE54hZcoqdEwkgi+m4Y02gqSJN/M3HMm5IB8jeYpakqllEylA55IeQW9L7CAcF2Z6+n4dUiaxn4vXdCtWfFrNoXeDUd3MeeqNFGkFfrc34vSNqXtUiVBa8G5Ot/PA9BvNvj8ogRAHchuRH/LoNXt2rSZnX3Tj02hakgnG4vq0xGwJQQKI3agx1nAjZV5eAgKBtQDFr3Ah0iyxzRRnQv6o01SgC1u/FmicAT2AcGtT7yHBHT05SnuONjsB9jK529SLUR0HNNPNcZjXSOiNwP9CtVQZrpgl/Y1WmukGAiEDq86ymKVZhjbDzt8RA5/hGDrinF7WDLKTCn7SilcM8I+bcTva+TuxJuFs8vwcd/VtXjI3i72PG4kDWEj3v+V+j3zXhRUwqpUR8nNfT85BevYYAL2gTMLIHecbxN5bwnOTUKiUrj4LcHEip35NH9s1xeNvVcxOhbWHQ6FquvS1+jo6xmKAa6576vADyCSSKx30Ja3dlrQ5VWXDHAIII90DaE7qLn8iSpD/B3n0JCn0Pnzq OCh59Zad p0dZnVcPZRqI1f0g= 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 Mon 09-01-23 15:16:27, Mel Gorman wrote: > A high-order ALLOC_HARDER allocation is assumed to be atomic. While that > is accurate, it changes later in the series. In preparation, explicitly > record high-order atomic allocations in gfp_to_alloc_flags(). There is > a slight functional change in that OOM handling avoids using high-order > reserve until it has to. I do not follow the oom handling part. IIRC we are dropping highatomic reserves before triggering oom. Something might have changed down the path but I can still see unreserve_highatomic_pageblock in should_reclaim_retry. I do not have any objection to ALLOC_HIGHATOMIC itself, though. > Signed-off-by: Mel Gorman > --- > mm/internal.h | 1 + > mm/page_alloc.c | 29 +++++++++++++++++++++++------ > 2 files changed, 24 insertions(+), 6 deletions(-) > > diff --git a/mm/internal.h b/mm/internal.h > index 403e4386626d..178484d9fd94 100644 > --- a/mm/internal.h > +++ b/mm/internal.h > @@ -746,6 +746,7 @@ unsigned int reclaim_clean_pages_from_list(struct zone *zone, > #else > #define ALLOC_NOFRAGMENT 0x0 > #endif > +#define ALLOC_HIGHATOMIC 0x200 /* Allows access to MIGRATE_HIGHATOMIC */ > #define ALLOC_KSWAPD 0x800 /* allow waking of kswapd, __GFP_KSWAPD_RECLAIM set */ > > enum ttu_flags; > diff --git a/mm/page_alloc.c b/mm/page_alloc.c > index 0040b4e00913..0ef4f3236a5a 100644 > --- a/mm/page_alloc.c > +++ b/mm/page_alloc.c > @@ -3706,10 +3706,20 @@ struct page *rmqueue_buddy(struct zone *preferred_zone, struct zone *zone, > * reserved for high-order atomic allocation, so order-0 > * request should skip it. > */ > - if (order > 0 && alloc_flags & ALLOC_HARDER) > + if (alloc_flags & ALLOC_HIGHATOMIC) > page = __rmqueue_smallest(zone, order, MIGRATE_HIGHATOMIC); > if (!page) { > page = __rmqueue(zone, order, migratetype, alloc_flags); > + > + /* > + * If the allocation fails, allow OOM handling access > + * to HIGHATOMIC reserves as failing now is worse than > + * failing a high-order atomic allocation in the > + * future. > + */ > + if (!page && (alloc_flags & ALLOC_OOM)) > + page = __rmqueue_smallest(zone, order, MIGRATE_HIGHATOMIC); > + > if (!page) { > spin_unlock_irqrestore(&zone->lock, flags); > return NULL; > @@ -4023,8 +4033,10 @@ bool __zone_watermark_ok(struct zone *z, unsigned int order, unsigned long mark, > return true; > } > #endif > - if (alloc_harder && !free_area_empty(area, MIGRATE_HIGHATOMIC)) > + if ((alloc_flags & (ALLOC_HIGHATOMIC|ALLOC_OOM)) && > + !free_area_empty(area, MIGRATE_HIGHATOMIC)) { > return true; > + } > } > return false; > } > @@ -4286,7 +4298,7 @@ get_page_from_freelist(gfp_t gfp_mask, unsigned int order, int alloc_flags, > * If this is a high-order atomic allocation then check > * if the pageblock should be reserved for the future > */ > - if (unlikely(order && (alloc_flags & ALLOC_HARDER))) > + if (unlikely(alloc_flags & ALLOC_HIGHATOMIC)) > reserve_highatomic_pageblock(page, zone, order); > > return page; > @@ -4813,7 +4825,7 @@ static void wake_all_kswapds(unsigned int order, gfp_t gfp_mask, > } > > static inline unsigned int > -gfp_to_alloc_flags(gfp_t gfp_mask) > +gfp_to_alloc_flags(gfp_t gfp_mask, unsigned int order) > { > unsigned int alloc_flags = ALLOC_WMARK_MIN | ALLOC_CPUSET; > > @@ -4839,8 +4851,13 @@ gfp_to_alloc_flags(gfp_t gfp_mask) > * Not worth trying to allocate harder for __GFP_NOMEMALLOC even > * if it can't schedule. > */ > - if (!(gfp_mask & __GFP_NOMEMALLOC)) > + if (!(gfp_mask & __GFP_NOMEMALLOC)) { > alloc_flags |= ALLOC_HARDER; > + > + if (order > 0) > + alloc_flags |= ALLOC_HIGHATOMIC; > + } > + > /* > * Ignore cpuset mems for GFP_ATOMIC rather than fail, see the > * comment for __cpuset_node_allowed(). > @@ -5048,7 +5065,7 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned int order, > * kswapd needs to be woken up, and to avoid the cost of setting up > * alloc_flags precisely. So we do that now. > */ > - alloc_flags = gfp_to_alloc_flags(gfp_mask); > + alloc_flags = gfp_to_alloc_flags(gfp_mask, order); > > /* > * We need to recalculate the starting point for the zonelist iterator > -- > 2.35.3 -- Michal Hocko SUSE Labs