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 3D5F5C4332F for ; Mon, 17 Jan 2022 18:09:38 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 3BBFC6B0072; Mon, 17 Jan 2022 13:09:37 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 36B3C6B0073; Mon, 17 Jan 2022 13:09:37 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 233036B0074; Mon, 17 Jan 2022 13:09:37 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0239.hostedemail.com [216.40.44.239]) by kanga.kvack.org (Postfix) with ESMTP id 119C06B0072 for ; Mon, 17 Jan 2022 13:09:37 -0500 (EST) Received: from smtpin09.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay03.hostedemail.com (Postfix) with ESMTP id 89628824C429 for ; Mon, 17 Jan 2022 18:09:36 +0000 (UTC) X-FDA: 79040566752.09.4163814 Received: from mail-lf1-f53.google.com (mail-lf1-f53.google.com [209.85.167.53]) by imf23.hostedemail.com (Postfix) with ESMTP id 2ED54140007 for ; Mon, 17 Jan 2022 18:09:36 +0000 (UTC) Received: by mail-lf1-f53.google.com with SMTP id b14so42264121lff.3 for ; Mon, 17 Jan 2022 10:09:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=aCBpQE3+WKAHFckl3pJBbXwBgqjJXxTRTSODJTXYv7Y=; b=nbREpN2YaeqLnZMVaW619Kq51fm9aWUkoukudf4cywftKptHH3Vsfw9n/3ft4bAsif QQ0w83Cs9R9F4HnP+26UedSOauMchTX03j320ASZUG+JdQ+AoVNLXF7LKPH8dGkqZ4ud Znva8zjFyPD6oYjl20ha16uTDgswsNBNsCAAcbYaLHjl5u08RBuldTmQGaOammODmlxI sf/cWQ0Dl5+eh8sK7iDN5wIJ6r0DC/3GHw729TSb5Nj1JAlzb9jcsAD9KupZq0vlv8xc 75Pq2qZ35W4unKVHgfIyr3AeF6SF17TmnWQkb1XUjEiS8Wf90RGI4sQltFBDNykbnG8u ORiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=aCBpQE3+WKAHFckl3pJBbXwBgqjJXxTRTSODJTXYv7Y=; b=Y/1OirOGH0yE+8P28Lmf143WI/N9OXaKuGAItv1hhNdEyO4Uz6HXDdP63qMRKxQMXI 4dnZVmeWq+fdMvMIeyOZNBvS17yGKTgk4dboupEtXJzX7nJgUFmm3GuHKjzLJ2Q/7Vdl BLRZV1te4ZRfcoGpOIRNdTssfXL/VkKsAlCchy7gl5nVsZ5qtiyRtWBJBL+0hEo0Lgri kPtCs2VpqIHa4y8+3XrNX80+1C4ZKU15NYkEYDo4ZOhKY+L7KNEMxmldrhV5KnJV+069 RS56z663EN6LcOpmD7NdKta9H1lP+q1X4mh4DF8QR1Vh3hIO0Nc90Cq90sd1UX1oPEQ5 HnQg== X-Gm-Message-State: AOAM532Ujrufilka5foW8A9FTMkLnE1V9dvxCP7tfemu0MwIufontEYi orj78gdPGnMOw0zHN7ONWNtD7q1rw/rSUZ6nw+zWoA== X-Google-Smtp-Source: ABdhPJzQDt9oG1pDNP+UePVmsbqVilT0eCroclyIpQ16Rn8UweQ7upS1R2bO7ir2v+uIbj3n61q3iqwI7YQKMRhMrjE= X-Received: by 2002:a05:6512:2629:: with SMTP id bt41mr17727678lfb.264.1642442974365; Mon, 17 Jan 2022 10:09:34 -0800 (PST) MIME-Version: 1.0 References: <20220115144150.1195590-1-shakeelb@google.com> In-Reply-To: From: Shakeel Butt Date: Mon, 17 Jan 2022 10:09:22 -0800 Message-ID: Subject: Re: [PATCH] mpage: remove ineffective __GFP_HIGH flag To: Christoph Hellwig Cc: Alexander Viro , Michal Hocko , Andrew Morton , Linux MM , LKML , linux-fsdevel Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 2ED54140007 X-Stat-Signature: wnwzh1fsoz684f1wuzkmjsy5efzz8331 Authentication-Results: imf23.hostedemail.com; dkim=pass header.d=google.com header.s=20210112 header.b=nbREpN2Y; dmarc=pass (policy=reject) header.from=google.com; spf=pass (imf23.hostedemail.com: domain of shakeelb@google.com designates 209.85.167.53 as permitted sender) smtp.mailfrom=shakeelb@google.com X-Rspamd-Server: rspam08 X-HE-Tag: 1642442976-55649 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000714, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Sun, Jan 16, 2022 at 11:15 PM Christoph Hellwig wrote: > > FYI, I have a patch removing mpage_alloc entirely as part of a bio > allocation refactoring series about to be sent out. So while your > analysis here is correct I'd prefer to hold this as the issue goes away > entirely. SGTM