linux-kernel - Re: [PATCH v16 0/9] mm / virtio: Provide support for free page reporting

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <cc71a016de155310f7593bfe3091eea094d400b4.camel@linux.intel.com>
Date:   Wed, 15 Jan 2020 15:08:45 -0800
From:   Alexander Duyck <alexander.h.duyck@...ux.intel.com>
To:     Alexander Duyck <alexander.duyck@...il.com>, kvm@...r.kernel.org,
        mst@...hat.com, linux-kernel@...r.kernel.org, willy@...radead.org,
        mhocko@...nel.org, linux-mm@...ck.org, akpm@...ux-foundation.org,
        mgorman@...hsingularity.net, vbabka@...e.cz
Cc:     yang.zhang.wz@...il.com, nitesh@...hat.com, konrad.wilk@...cle.com,
        david@...hat.com, pagupta@...hat.com, riel@...riel.com,
        lcapitulino@...hat.com, dave.hansen@...el.com,
        wei.w.wang@...el.com, aarcange@...hat.com, pbonzini@...hat.com,
        dan.j.williams@...el.com, osalvador@...e.de
Subject: Re: [PATCH v16 0/9] mm / virtio: Provide support for free page
 reporting

On Fri, 2020-01-03 at 13:16 -0800, Alexander Duyck wrote:
> This series provides an asynchronous means of reporting free guest pages
> to a hypervisor so that the memory associated with those pages can be
> dropped and reused by other processes and/or guests on the host. Using
> this it is possible to avoid unnecessary I/O to disk and greatly improve
> performance in the case of memory overcommit on the host.

<snip>

> 
> Changes from v15:
> https://lore.kernel.org/lkml/20191205161928.19548.41654.stgit@localhost.localdomain/
> Rebased on linux-next-20191219
> Split out patches for budget and moving head to last page processed
>   Updated budget code to reduce how much memory is reported per pass
>   Added logic to also rotate the list if we exit due a page isolation failure
> Added migratetype as argument in __putback_isolated_page

It's been about a week and a half since I posted the set and haven't
really gotten much feedback other than a suggestion of a slight tweak to
the titles for patches 7 & 8 to mention page_reporting. I'm mainly looking
for input on patches 3, 4, 7 and 8 since those are the ones that contain
most of the changes based on recent feedback.

I'm wondering if there is any remaining concerns or if these patches are
in a state where they are ready to be pulled into the MM tree?

Thanks.

- Alex