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 8C7D8C433F5 for ; Tue, 1 Mar 2022 16:22:15 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id C3E428D0002; Tue, 1 Mar 2022 11:22:14 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id BED808D0001; Tue, 1 Mar 2022 11:22:14 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id AB6A48D0002; Tue, 1 Mar 2022 11:22:14 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.hostedemail.com [64.99.140.25]) by kanga.kvack.org (Postfix) with ESMTP id 9C2878D0001 for ; Tue, 1 Mar 2022 11:22:14 -0500 (EST) Received: from smtpin01.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay02.hostedemail.com (Postfix) with ESMTP id 69D6C23F47 for ; Tue, 1 Mar 2022 16:22:14 +0000 (UTC) X-FDA: 79196334588.01.9B11643 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by imf15.hostedemail.com (Postfix) with ESMTP id B164CA000B for ; Tue, 1 Mar 2022 16:22:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1646151733; h=from:from: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:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=VpcEjZ3pDaEx12dH+BduTDFR/D5IwkR6BCpw7XkWHU0=; b=gPj0/G4JttlA8PIQES5HkDDGyu7uuI/AAEmsvq0Hk8ohCU/RLGKsP6/YiL2g4O6GUdD0bB loFPbqzt5gEdJqWOCGMDiBbKONP0mEFjxO8onZ2mdXfY8q275EqPgcN5ya+iLPK4ku16Bw UxKS7T4cqfJkfG1cr4i1U0AdoJ+VRZo= Received: from mail-wr1-f69.google.com (mail-wr1-f69.google.com [209.85.221.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-583-KTsXV_GLM8aaf8Rn87_r0Q-1; Tue, 01 Mar 2022 11:22:12 -0500 X-MC-Unique: KTsXV_GLM8aaf8Rn87_r0Q-1 Received: by mail-wr1-f69.google.com with SMTP id c5-20020adffb05000000b001edbbefe96dso3483231wrr.8 for ; Tue, 01 Mar 2022 08:22:11 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:organization:in-reply-to :content-transfer-encoding; bh=VpcEjZ3pDaEx12dH+BduTDFR/D5IwkR6BCpw7XkWHU0=; b=YuotjXr9Bp9uXsVehPtCQ57L+5VlOSDMfVmyMakEgCNpcEQOe69K24zVw2nXGrbxZ1 GKHBPh9oqufrbRftziAp6t8gOPkqWVl4Ry0cgcDNaw7uqiYXe4Ifodyna1tQbuPbZpmT XjNaKcXFa3IzotRQpXl+9YaSDMh/j+48cA1zWdMh0KV/dmywoShYusvpdSuLPaHcHoNU 3DzJgQtvs97VRdz5ibVpjwjx/3Sle0BJxN5laf1mV+WpfYGYoFdPEux6zIg9LK3rkUgm AWeJjwaNe6iumkWNagYuYl80uWLT4W4KffKzkPNI7YIETLmQqUwtZAyWrPHvGETATCte Fzdg== X-Gm-Message-State: AOAM531HkA2t7qdGN36AbzDCLh4+ZY7+AH5j5fL6+H9qrM1yC2VPFCZ2 7EY+uVP1OcVw1CkB2C2ZFukF20Tse6l4jclGJ9g3t1Gs8k5Mcpy9jCQ8ut1GYq4ONvW9caSGJ6Y cb1gJhuNImeg= X-Received: by 2002:a05:600c:1e03:b0:381:4134:35ca with SMTP id ay3-20020a05600c1e0300b00381413435camr14983726wmb.145.1646151730958; Tue, 01 Mar 2022 08:22:10 -0800 (PST) X-Google-Smtp-Source: ABdhPJxYfHVRSOGMfPLPfHkM21n2ADlCruTETrhJPt1WIhsU9tWlvnq+Hh/dL+h6goFY71nLBUFD/w== X-Received: by 2002:a05:600c:1e03:b0:381:4134:35ca with SMTP id ay3-20020a05600c1e0300b00381413435camr14983702wmb.145.1646151730682; Tue, 01 Mar 2022 08:22:10 -0800 (PST) Received: from ?IPV6:2003:cb:c70e:5e00:88ce:ad41:cb1b:323? (p200300cbc70e5e0088cead41cb1b0323.dip0.t-ipconnect.de. [2003:cb:c70e:5e00:88ce:ad41:cb1b:323]) by smtp.gmail.com with ESMTPSA id g6-20020a05600c4ec600b0037bf934bca3sm3706698wmq.17.2022.03.01.08.22.08 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 01 Mar 2022 08:22:10 -0800 (PST) Message-ID: Date: Tue, 1 Mar 2022 17:22:08 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: [PATCH] mm: split vm_normal_pages for LRU and non-LRU handling To: Felix Kuehling , Alex Sierra , jgg@nvidia.com Cc: linux-mm@kvack.org, rcampbell@nvidia.com, linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org, amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, hch@lst.de, jglisse@redhat.com, apopple@nvidia.com, willy@infradead.org, akpm@linux-foundation.org References: <20220218192640.GV4160@nvidia.com> <20220228203401.7155-1-alex.sierra@amd.com> <2a042493-d04d-41b1-ea12-b326d2116861@redhat.com> <41469645-55be-1aaa-c1ef-84a123fdb4ea@amd.com> From: David Hildenbrand Organization: Red Hat In-Reply-To: <41469645-55be-1aaa-c1ef-84a123fdb4ea@amd.com> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspam-User: X-Rspamd-Server: rspam04 X-Rspamd-Queue-Id: B164CA000B X-Stat-Signature: 64j6mwqw8oxibjfuu6jjayqx54tsiba3 Authentication-Results: imf15.hostedemail.com; dkim=pass header.d=redhat.com header.s=mimecast20190719 header.b="gPj0/G4J"; spf=none (imf15.hostedemail.com: domain of david@redhat.com has no SPF policy when checking 170.10.129.124) smtp.mailfrom=david@redhat.com; dmarc=pass (policy=none) header.from=redhat.com X-HE-Tag: 1646151733-739135 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: >> >>> if (PageReserved(page)) >>> diff --git a/mm/migrate.c b/mm/migrate.c >>> index c31d04b46a5e..17d049311b78 100644 >>> --- a/mm/migrate.c >>> +++ b/mm/migrate.c >>> @@ -1614,7 +1614,7 @@ static int add_page_for_migration(struct mm_struct *mm, unsigned long addr, >>> goto out; >>> >>> /* FOLL_DUMP to ignore special (like zero) pages */ >>> - follflags = FOLL_GET | FOLL_DUMP; >>> + follflags = FOLL_GET | FOLL_DUMP | FOLL_LRU; >>> page = follow_page(vma, addr, follflags); >> Why wouldn't we want to dump DEVICE_COHERENT pages? This looks wrong. > > This function later calls isolate_lru_page, which is something you can't > do with a device page. > Then, that code might require care instead. We most certainly don't want to have random memory holes in a dump just because some anonymous memory was migrated to DEVICE_COHERENT. -- Thanks, David / dhildenb