From: Alexander Duyck <alexander.h.duyck@linux.intel.com>
To: Alexander Duyck <alexander.duyck@gmail.com>,
kvm@vger.kernel.org, mst@redhat.com,
linux-kernel@vger.kernel.org, willy@infradead.org,
mhocko@kernel.org, linux-mm@kvack.org, akpm@linux-foundation.org,
mgorman@techsingularity.net, vbabka@suse.cz
Cc: yang.zhang.wz@gmail.com, nitesh@redhat.com,
konrad.wilk@oracle.com, david@redhat.com, pagupta@redhat.com,
riel@surriel.com, lcapitulino@redhat.com, dave.hansen@intel.com,
wei.w.wang@intel.com, aarcange@redhat.com, pbonzini@redhat.com,
dan.j.williams@intel.com, osalvador@suse.de
Subject: Re: [PATCH v16 0/9] mm / virtio: Provide support for free page reporting
Date: Wed, 15 Jan 2020 15:08:45 -0800 [thread overview]
Message-ID: <cc71a016de155310f7593bfe3091eea094d400b4.camel@linux.intel.com> (raw)
In-Reply-To: <20200103210509.29237.18426.stgit@localhost.localdomain>
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
prev parent reply other threads:[~2020-01-15 23:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 21:16 [PATCH v16 0/9] mm / virtio: Provide support for free page reporting Alexander Duyck
2020-01-03 21:16 ` [PATCH v16 1/9] mm: Adjust shuffle code to allow for future coalescing Alexander Duyck
2020-01-03 21:16 ` [PATCH v16 2/9] mm: Use zone and order instead of free area in free_list manipulators Alexander Duyck
2020-01-03 21:16 ` [PATCH v16 3/9] mm: Add function __putback_isolated_page Alexander Duyck
2020-01-03 21:16 ` [PATCH v16 4/9] mm: Introduce Reported pages Alexander Duyck
2020-01-03 21:16 ` [PATCH v16 5/9] virtio-balloon: Pull page poisoning config out of free page hinting Alexander Duyck
2020-01-03 21:16 ` [PATCH v16 6/9] virtio-balloon: Add support for providing free page reports to host Alexander Duyck
2020-01-03 21:16 ` [PATCH v16 7/9] mm: Rotate free list so reported pages are moved to the tail of the list Alexander Duyck
2020-01-08 13:38 ` David Hildenbrand
2020-01-08 16:07 ` Alexander Duyck
2020-01-03 21:17 ` [PATCH v16 8/9] mm: Add budget limit to how many pages can be reported per list per pass Alexander Duyck
2020-01-03 21:17 ` [PATCH v16 9/9] mm: Add free page reporting documentation Alexander Duyck
2020-01-03 21:21 ` [PATCH v16 QEMU 1/3] virtio-ballon: Implement support for page poison tracking feature Alexander Duyck
2020-01-03 21:21 ` [PATCH v16 QEMU 2/3] virtio-balloon: Add support for providing free page reports to host Alexander Duyck
2020-01-03 21:21 ` [PATCH v16 QEMU 3/3] virtio-balloon: Provide a interface for free page reporting Alexander Duyck
2020-01-03 21:24 ` [PATCH v16 QEMU 4/3 RFC] memory: Add support for MADV_FREE as mechanism to lazy discard pages Alexander Duyck
2020-01-08 7:57 ` [PATCH v16 0/9] mm / virtio: Provide support for free page reporting Nitesh Narayan Lal
2020-01-08 16:29 ` Alexander Duyck
2020-01-15 23:08 ` Alexander Duyck [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cc71a016de155310f7593bfe3091eea094d400b4.camel@linux.intel.com \
--to=alexander.h.duyck@linux.intel.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.duyck@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=david@redhat.com \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=mst@redhat.com \
--cc=nitesh@redhat.com \
--cc=osalvador@suse.de \
--cc=pagupta@redhat.com \
--cc=pbonzini@redhat.com \
--cc=riel@surriel.com \
--cc=vbabka@suse.cz \
--cc=wei.w.wang@intel.com \
--cc=willy@infradead.org \
--cc=yang.zhang.wz@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).