Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp2719279ybb; Mon, 30 Mar 2020 11:32:10 -0700 (PDT) X-Google-Smtp-Source: ADFU+vuavcAtiFwui+gLH3FXBc2eyTWfLX/WpxctqsQutiyqLeoQMlbPAEUykStXLveohFdDqEmO X-Received: by 2002:aca:c45:: with SMTP id i5mr450186oiy.101.1585593130107; Mon, 30 Mar 2020 11:32:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585593130; cv=none; d=google.com; s=arc-20160816; b=fIbAYhVvsCTZ90A/6J4EycEQhqaSxmQrWXqehKx4PV/RWAxje5eWz+4UosgpBcGfDI HJfkEcvCTuJXyWVXammv6XNYiYS5YIaQ3I9pGJEisXMQ7xcSlgtS58K5ZlTJXEsvp8vx v8Q766m+4T4g6ViRoaIpWLFiXxsnqIr7RFDGJSy/49NJlunAtG9hLAbJIDJt7COqOdRZ QgXpbLLU6+8PWLxq38Vunk9R7iyVaaw+79hf5xfC1SjOTTUT9T4U5BjgctgsKEYN6+me LQblpYCyi4I09/LYF2YRJzNrA27sN/PflCDElmMgxbojDV8Z6MwjTFZnXGKE8gpx/pFO hR3Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=zSbITaAyAzmhAT6gpCYOeXzgKkCsXrLUD6omquEuTqY=; b=VvDwBxXjDgpOqiDrb7Pd3UMtV99CNpCxOdF1N0h9gfd1zcDJX43c5XFNQxDU8Xy0Ud fT0GYsc24xI2+yeeNrCYO7ywd99RlvnyrOvre7Mgd5U112/ImVJsCPCCTsN6Fog4SKOE WSNcQqVadCn+oDm4MCRMfZcansTc/TbdgyQBEQtWQ4jg4YSIRNE2JNSLVwWY1T8eVSzV ZKIylty2goaLzViOtFjrkPaVn/0I8/EEMF9DWXRxP1B3sYoWKL3aNBoddq5nNcUVtwQp U/WuSKucfhq/FmaENk2FclGdorauHnFGNsmlq/69ymnz7aJLbuy07FNTJKTcgSpYGyW9 SabA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=WJa5CITi; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x25si6493542otk.160.2020.03.30.11.31.55; Mon, 30 Mar 2020 11:32:10 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=WJa5CITi; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727806AbgC3Sa2 (ORCPT + 99 others); Mon, 30 Mar 2020 14:30:28 -0400 Received: from mail-ed1-f65.google.com ([209.85.208.65]:46200 "EHLO mail-ed1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726518AbgC3Sa2 (ORCPT ); Mon, 30 Mar 2020 14:30:28 -0400 Received: by mail-ed1-f65.google.com with SMTP id cf14so21947127edb.13 for ; Mon, 30 Mar 2020 11:30:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zSbITaAyAzmhAT6gpCYOeXzgKkCsXrLUD6omquEuTqY=; b=WJa5CITi4iYXQT1Z7o4OzTgnLf9uIecH9M0QpLD3CUdOq7e664RYV+SuoFfPVnNH3o KiKmmmBeZNXR+i4pwta9kGEry09HnXz+ABQ6KJk0t/REVFppsHl27jPJSpg0sWDoRcW6 CXpQRfWPIGJuf3Y8VzLa8/MrBYSe/VkaONHzl3trkyhkyFxkzpbDEAHVB1PxcnGyf78Z GgjDy9diqWeW/QAOyksDi0LUSQ6Ksne7EhwnKhF/6hCmqNWg4v6aDnMOZXz4qCtjC2a1 4UCj+xFpG1F9Rk+QYsnBJgE672PIOTGV+WQSbnr1fYytOk2aEaPEnFjqi7l1W4HklniK I/kA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zSbITaAyAzmhAT6gpCYOeXzgKkCsXrLUD6omquEuTqY=; b=Pg0suV6RxFtu+u9JXrtChEGogCBhfG3lzqEjCepUN2i57raK1wsTlt6pinm2tHpSun ALqeQ3GfOX7Wl07jWTaUWa5WfUI2XWfg35En+Bp9MqCLaXKE9I/Gy4WEnI4BZd04nQ4d Yccq28xaGfe5QRS4fnN+Q9JopMdhZRU9amRzN8lAkQhdcc8EFemqXuGTCSIeBy5yQVp2 ORgZqHpYspageLRM8sfvKG5MhGpGLlfW5uT1AmkwlPj68pwTWT2jTZYfnULoiFF4Cmer AcIKaDoOeXvAJxjJIyfkBBEvrF9Jm1N9yoUY3BaAr10+0us3FaXZLM8k1fgoFnFI+y2C eQ/A== X-Gm-Message-State: ANhLgQ0ZBYuRxQsvu/pxgWNrSUtwS/ZGo9EMHHEsiSl/SES45IgxSs75 aMqRymcvX6dE6zJz9hzEYw2s6GC0zNvfWlmgmpXoK5s6 X-Received: by 2002:a17:906:d7a6:: with SMTP id pk6mr6255024ejb.309.1585593026220; Mon, 30 Mar 2020 11:30:26 -0700 (PDT) MIME-Version: 1.0 References: <20200327170601.18563-1-kirill.shutemov@linux.intel.com> <20200327170601.18563-4-kirill.shutemov@linux.intel.com> <20200328121829.kzmcmcshbwynjmqc@box> In-Reply-To: <20200328121829.kzmcmcshbwynjmqc@box> From: Yang Shi Date: Mon, 30 Mar 2020 11:30:14 -0700 Message-ID: Subject: Re: [PATCH 3/7] khugepaged: Drain LRU add pagevec to get rid of extra pins To: "Kirill A. Shutemov" Cc: Andrew Morton , Andrea Arcangeli , Linux MM , Linux Kernel Mailing List , "Kirill A. Shutemov" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Mar 28, 2020 at 5:18 AM Kirill A. Shutemov wrote: > > On Fri, Mar 27, 2020 at 11:10:40AM -0700, Yang Shi wrote: > > On Fri, Mar 27, 2020 at 10:06 AM Kirill A. Shutemov > > wrote: > > > > > > __collapse_huge_page_isolate() may fail due to extra pin in the LRU add > > > pagevec. It's petty common for swapin case: we swap in pages just to > > > fail due to the extra pin. > > > > > > Signed-off-by: Kirill A. Shutemov > > > --- > > > mm/khugepaged.c | 8 ++++++++ > > > 1 file changed, 8 insertions(+) > > > > > > diff --git a/mm/khugepaged.c b/mm/khugepaged.c > > > index 14d7afc90786..39e0994abeb8 100644 > > > --- a/mm/khugepaged.c > > > +++ b/mm/khugepaged.c > > > @@ -585,11 +585,19 @@ static int __collapse_huge_page_isolate(struct vm_area_struct *vma, > > > * The page must only be referenced by the scanned process > > > * and page swap cache. > > > */ > > > + if (page_count(page) != 1 + PageSwapCache(page)) { > > > + /* > > > + * Drain pagevec and retry just in case we can get rid > > > + * of the extra pin, like in swapin case. > > > + */ > > > + lru_add_drain(); > > > > This is definitely correct. > > > > I'm wondering if we need one more lru_add_drain() before PageLRU check > > in khugepaged_scan_pmd() or not? The page might be in lru cache then > > get skipped. This would improve the success rate. > > Could you elaborate on the scenario, I don't follow. I mean the below change: --- a/mm/khugepaged.c +++ b/mm/khugepaged.c @@ -1195,6 +1195,9 @@ static int khugepaged_scan_pmd(struct mm_struct *mm, goto out_unmap; } khugepaged_node_load[node]++; + if (!PageLRU(page)) + /* Flush the page out of lru cache */ + lru_add_drain(); if (!PageLRU(page)) { result = SCAN_PAGE_LRU; goto out_unmap; If the page is not on LRU we even can't reach collapse_huge_page(), right? > > > -- > Kirill A. Shutemov