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 E5825C433EF for ; Wed, 23 Feb 2022 19:07:57 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 605538D004B; Wed, 23 Feb 2022 14:07:57 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 58AD58D0011; Wed, 23 Feb 2022 14:07:57 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 404798D004B; Wed, 23 Feb 2022 14:07:57 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0032.hostedemail.com [216.40.44.32]) by kanga.kvack.org (Postfix) with ESMTP id 13F548D0011 for ; Wed, 23 Feb 2022 14:07:57 -0500 (EST) Received: from smtpin12.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay02.hostedemail.com (Postfix) with ESMTP id B26AEA0A25 for ; Wed, 23 Feb 2022 19:07:56 +0000 (UTC) X-FDA: 79174979352.12.FC9C3EB Received: from mail-yb1-f175.google.com (mail-yb1-f175.google.com [209.85.219.175]) by imf17.hostedemail.com (Postfix) with ESMTP id A2D7A40015 for ; Wed, 23 Feb 2022 19:06:30 +0000 (UTC) Received: by mail-yb1-f175.google.com with SMTP id u12so36039733ybd.7 for ; Wed, 23 Feb 2022 11:06:30 -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=4xZqFmgf5/y8vSfdSXKXHJcVwPPK/T+ncXD/Q/6tYGs=; b=SdOczIhsiozsDQKULdBWj+vfCmfMwIq/TcMjZnslL6+RJVqTDPbo/VmZqa1IK9y1rO gvWavvEgs24VLisDTz3ETDhfYpLHwH2J0Hh2q0d8x1TOiGoUjc8oG6QPptFrZAg3jl2F w+v7qqxMf/XiKM7YSlk3LIytHLzLjVkAzwAGnwuZQGxZKrQ8sOdc6nvcgYJrvl/rrdad DQtOKFWBcmLDf1F+KI6x7I9yU3dSTLN8P6nHK2lqoAuGBMF3ojRFwBb6o7/LP9K4aoHz 8WQarOhHIzKoVkCkJJxHcEYRM096dT5tIhzDKzoDrxL4TYWTRxtNYEWh5xesLwulGvGo rLvw== 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=4xZqFmgf5/y8vSfdSXKXHJcVwPPK/T+ncXD/Q/6tYGs=; b=tuwpqKXcAPIkYxf0VMjZJdi97iOunBtIHYWVkFTgtnlSvgeFDw1LmadYEyri6dO5I0 OCAVUrvhT73o0eJ9v6dV4P41DWYdXCk52P2wZwN9FWCEX19E6gEJr6SLD+r6hOrQflox mFqJ+5q1qe7Z67B4uByFG0nPLYp4dPt8BjzS3sxjtvisilvWVd2DMIS/Rj+3OqDrJSDh ptRw+HyCGkg0xyDaWVB62WwbESpA4EUNbacB0r2FHLtgpiDM7HLiPSFXmrR0tOB6pFlE /egl7lnEJO29r0RZX5uK++ZDXtg+U8ega4DtGEBtu5SS51rxlO5xcqhICRo7eBowbIwI 2tAw== X-Gm-Message-State: AOAM531ufXMI/DrXaT0i41TH6Q9fXTexF+XowLNwkKb2XW9GrG/GpWiI iaUE8Uz1zFmdXQ5BWQ3S4LMSM5972Um/pS1XO1DOLQ== X-Google-Smtp-Source: ABdhPJz64yAvdnJk1+Xmpn0rwuJJGqln3QrsMUh4KE/EdaMATdk2S7A5EDux1DopRlcc+Ztlo+jG4OAgerZ5VKeQZpI= X-Received: by 2002:a25:d986:0:b0:624:ddc:ff9 with SMTP id q128-20020a25d986000000b006240ddc0ff9mr990227ybg.509.1645643189482; Wed, 23 Feb 2022 11:06:29 -0800 (PST) MIME-Version: 1.0 References: <20220219174940.2570901-1-surenb@google.com> In-Reply-To: From: Suren Baghdasaryan Date: Wed, 23 Feb 2022 11:06:18 -0800 Message-ID: Subject: Re: [PATCH 1/1] mm: count time in drain_all_pages during direct reclaim as memory pressure To: Johannes Weiner Cc: Minchan Kim , akpm@linux-foundation.org, mhocko@suse.com, peterz@infradead.org, guro@fb.com, shakeelb@google.com, timmurray@google.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, kernel-team@android.com Content-Type: text/plain; charset="UTF-8" X-Rspam-User: Authentication-Results: imf17.hostedemail.com; dkim=pass header.d=google.com header.s=20210112 header.b=SdOczIhs; spf=pass (imf17.hostedemail.com: domain of surenb@google.com designates 209.85.219.175 as permitted sender) smtp.mailfrom=surenb@google.com; dmarc=pass (policy=reject) header.from=google.com X-Rspamd-Server: rspam08 X-Rspamd-Queue-Id: A2D7A40015 X-Stat-Signature: dd1p1g5wbewh1mcpmstzfiezd8yrxawg X-HE-Tag: 1645643190-61299 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, Feb 23, 2022 at 10:54 AM Johannes Weiner wrote: > > On Sun, Feb 20, 2022 at 08:52:38AM -0800, Suren Baghdasaryan wrote: > > On Sat, Feb 19, 2022 at 4:40 PM Minchan Kim wrote: > > > > > > On Sat, Feb 19, 2022 at 09:49:40AM -0800, Suren Baghdasaryan wrote: > > > > When page allocation in direct reclaim path fails, the system will > > > > make one attempt to shrink per-cpu page lists and free pages from > > > > high alloc reserves. Draining per-cpu pages into buddy allocator can > > > > be a very slow operation because it's done using workqueues and the > > > > task in direct reclaim waits for all of them to finish before > > > > > > Yes, drain_all_pages is serious slow(100ms - 150ms on Android) > > > especially when CPUs are fully packed. It was also spotted in CMA > > > allocation even when there was on no memory pressure. > > > > Thanks for the input, Minchan! > > In my tests I've seen 50-60ms delays in a single drain_all_pages but I > > can imagine there are cases worse than these. > > > > > > > > > proceeding. Currently this time is not accounted as psi memory stall. > > > > > > Good spot. > > > > > > > > > > > While testing mobile devices under extreme memory pressure, when > > > > allocations are failing during direct reclaim, we notices that psi > > > > events which would be expected in such conditions were not triggered. > > > > After profiling these cases it was determined that the reason for > > > > missing psi events was that a big chunk of time spent in direct > > > > reclaim is not accounted as memory stall, therefore psi would not > > > > reach the levels at which an event is generated. Further investigation > > > > revealed that the bulk of that unaccounted time was spent inside > > > > drain_all_pages call. > > > > > > > > Annotate drain_all_pages and unreserve_highatomic_pageblock during > > > > page allocation failure in the direct reclaim path so that delays > > > > caused by these calls are accounted as memory stall. > > > > > > > > Reported-by: Tim Murray > > > > Signed-off-by: Suren Baghdasaryan > > > > --- > > > > mm/page_alloc.c | 4 ++++ > > > > 1 file changed, 4 insertions(+) > > > > > > > > diff --git a/mm/page_alloc.c b/mm/page_alloc.c > > > > index 3589febc6d31..7fd0d392b39b 100644 > > > > --- a/mm/page_alloc.c > > > > +++ b/mm/page_alloc.c > > > > @@ -4639,8 +4639,12 @@ __alloc_pages_direct_reclaim(gfp_t gfp_mask, unsigned int order, > > > > * Shrink them and try again > > > > */ > > > > if (!page && !drained) { > > > > + unsigned long pflags; > > > > + > > > > + psi_memstall_enter(&pflags); > > > > unreserve_highatomic_pageblock(ac, false); > > > > drain_all_pages(NULL); > > > > + psi_memstall_leave(&pflags); > > > > > > Instead of annotating the specific drain_all_pages, how about > > > moving the annotation from __perform_reclaim to > > > __alloc_pages_direct_reclaim? > > > > I'm fine with that approach too. Let's wait for Johannes' input before > > I make any changes. > > I think the change makes sense, even if the workqueue fix speeds up > the drain. I agree with Minchan about moving the annotation upward. > > With it moved, please feel free to add > Acked-by: Johannes Weiner Thanks Johannes! I'll move psi_memstall_enter/psi_memstall_leave from __perform_reclaim into __alloc_pages_direct_reclaim to cover it completely. After that will continue on fixing the workqueue issue.