Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp1266470rwb; Thu, 8 Dec 2022 08:33:17 -0800 (PST) X-Google-Smtp-Source: AA0mqf5FxYaLJMKwiaV/rp6gKFFxJ5ObrqQByvyHhKniUgVec/ef3mTb3yJnN1PbyZ0chAq9MaUd X-Received: by 2002:a05:6a00:3385:b0:56c:309:b900 with SMTP id cm5-20020a056a00338500b0056c0309b900mr76276451pfb.21.1670517196978; Thu, 08 Dec 2022 08:33:16 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1670517196; cv=none; d=google.com; s=arc-20160816; b=Dy3k/V3jAhijk7k5P+WoTbtSoPQXZADhN9MvkIrSxS7jutqjR8awBV7fqXWD1mrKe8 rYLJXprwvSgvHWgsdc+o7mxKUjPTUMEK1l64j1N2p+3eiMWJD4ME0YaVwUzi11mUa/HU 5nqgR+HXKlkaL13plVZ3Hbg06GLnLg+A9bLtPzYpxr+nhuXyHW431PRncnz4nAmi/sul KmiiMyYXFX3OzPtE8y7I1/bk3YjsGtcLQcKPxFwMOQUq6f8mbzo8HHg5Oc79+ABYKSqm ZqFF+tVfXB49EJEkcpPunPOJBWWp3KbZxfo4ayPLeud1IEmTep2usgD6j2Wa/+yKjAQj vCOw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature:dkim-signature; bh=tRLagXkKmeXcUI+MhtRhuiGQoB9TArlcDvyl6UUGYBk=; b=eryL5LkCu+v23RPHIoAzPolZSNO2F/qrPHqAA5QA3u3DezWPH96UOhNNGWyR1h+kaY GJDvJP21Us02NTq/mfbsCc5npfzsnboyR8Jp/2JyhcT3s2IZuNbQQaAaKgQEoSvLxhEe kmIsqoAxwz+jDA+LoUdWd6Oas4BkPHW/Xu4NUfzuEjONwhgTUqiDlXphsSfrv5HNtFXe /kSpsDoJVBnPKhzh8jFpHT6WH3SbB9SLJAP+ne+hEhZyNgvxL8a4YyvcaGBLsW66E3ha +LYf2Jp6SmvK09A4HPZw2CdwmVU/W+yqfrQhVC4NcD8CQ+WE1JeyVhSN76qc5t39h0nL dclQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=vQM6oCgC; dkim=neutral (no key) header.i=@suse.cz header.s=susede2_ed25519 header.b="cqPa/291"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id v185-20020a6389c2000000b00478ed620d12si5905169pgd.777.2022.12.08.08.33.07; Thu, 08 Dec 2022 08:33:16 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=vQM6oCgC; dkim=neutral (no key) header.i=@suse.cz header.s=susede2_ed25519 header.b="cqPa/291"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230137AbiLHQQJ (ORCPT + 72 others); Thu, 8 Dec 2022 11:16:09 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58556 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229854AbiLHQQI (ORCPT ); Thu, 8 Dec 2022 11:16:08 -0500 Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4334BAD992 for ; Thu, 8 Dec 2022 08:16:06 -0800 (PST) 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 720B7208B2; Thu, 8 Dec 2022 16:16:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1670516165; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=tRLagXkKmeXcUI+MhtRhuiGQoB9TArlcDvyl6UUGYBk=; b=vQM6oCgCOVXwFV5DYj98yA29qsTLcOVugq//N1Aabe0iC9QaR9hMXQXRHW9mQYoqGZgF33 sR6aoF0IInhAbFtJdd+EAbuj+GHUg5FcKuDaLsMLkd27eKX05tiQyxmp4aOK2pd0xzy9wn lYiYYR6749emvc3Kvv+7/Lem33Zde/A= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1670516165; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=tRLagXkKmeXcUI+MhtRhuiGQoB9TArlcDvyl6UUGYBk=; b=cqPa/291QA0081oNI9E26jjdK0TvifhhMFbqCpEj0LsO1hZfyXg//NECr7lDppmi5C2ZqI +g8Fl6QDdhdO3YDg== 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 52C8C138E0; Thu, 8 Dec 2022 16:16:05 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id 6hiEE8UNkmN7IQAAMHmgww (envelope-from ); Thu, 08 Dec 2022 16:16:05 +0000 Message-ID: Date: Thu, 8 Dec 2022 17:16:05 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.1 Subject: Re: [PATCH 2/6] mm/page_alloc: Treat RT tasks similar to GFP_HIGH Content-Language: en-US To: Mel Gorman , Linux-MM Cc: Andrew Morton , Michal Hocko , NeilBrown , Thierry Reding , Matthew Wilcox , LKML References: <20221129151701.23261-1-mgorman@techsingularity.net> <20221129151701.23261-3-mgorman@techsingularity.net> From: Vlastimil Babka In-Reply-To: <20221129151701.23261-3-mgorman@techsingularity.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Subject should say __GFP_HIGH as there's no GFP_HIGH? On 11/29/22 16:16, Mel Gorman wrote: > RT tasks are allowed to dip below the min reserve but ALLOC_HARDER is > typically combined with ALLOC_MIN_RESERVE so RT tasks are a little > unusual. While there is some justification for allowing RT tasks > access to memory reserves, there is a strong chance that a RT task > that is also under memory pressure is at risk of missing deadlines > anyway. Relax how much reserves an RT task can access by treating > it the same as __GFP_HIGH allocations. > > Signed-off-by: Mel Gorman Acked-by: Vlastimil Babka > --- > mm/page_alloc.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/mm/page_alloc.c b/mm/page_alloc.c > index 3b37909617bc..da746e9eb2cf 100644 > --- a/mm/page_alloc.c > +++ b/mm/page_alloc.c > @@ -4852,7 +4852,7 @@ gfp_to_alloc_flags(gfp_t gfp_mask) > */ > alloc_flags &= ~ALLOC_CPUSET; > } else if (unlikely(rt_task(current)) && in_task()) > - alloc_flags |= ALLOC_HARDER; > + alloc_flags |= ALLOC_MIN_RESERVE; > > alloc_flags = gfp_to_alloc_flags_cma(gfp_mask, alloc_flags); >