From: Nitesh Narayan Lal <nitesh@redhat.com>
To: Alexander Duyck <alexander.duyck@gmail.com>,
kvm@vger.kernel.org, david@redhat.com, mst@redhat.com,
dave.hansen@intel.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, akpm@linux-foundation.org
Cc: yang.zhang.wz@gmail.com, pagupta@redhat.com, riel@surriel.com,
konrad.wilk@oracle.com, willy@infradead.org,
lcapitulino@redhat.com, wei.w.wang@intel.com,
aarcange@redhat.com, pbonzini@redhat.com,
dan.j.williams@intel.com, alexander.h.duyck@linux.intel.com
Subject: Re: [PATCH v3 0/6] mm / virtio: Provide support for unused page reporting
Date: Fri, 2 Aug 2019 10:41:24 -0400 [thread overview]
Message-ID: <9cddf98d-e2ce-0f8a-d46c-e15a54bc7391@redhat.com> (raw)
In-Reply-To: <20190801222158.22190.96964.stgit@localhost.localdomain>
On 8/1/19 6:24 PM, Alexander Duyck wrote:
> This series provides an asynchronous means of reporting to a hypervisor
> that a guest page is no longer in use and can have the data associated
> with it dropped. To do this I have implemented functionality that allows
> for what I am referring to as unused page reporting
>
> The functionality for this is fairly simple. When enabled it will allocate
> statistics to track the number of reported pages in a given free area.
> When the number of free pages exceeds this value plus a high water value,
> currently 32, it will begin performing page reporting which consists of
> pulling pages off of free list and placing them into a scatter list. The
> scatterlist is then given to the page reporting device and it will perform
> the required action to make the pages "reported", in the case of
> virtio-balloon this results in the pages being madvised as MADV_DONTNEED
> and as such they are forced out of the guest. After this they are placed
> back on the free list, and an additional bit is added if they are not
> merged indicating that they are a reported buddy page instead of a
> standard buddy page. The cycle then repeats with additional non-reported
> pages being pulled until the free areas all consist of reported pages.
>
> I am leaving a number of things hard-coded such as limiting the lowest
> order processed to PAGEBLOCK_ORDER, and have left it up to the guest to
> determine what the limit is on how many pages it wants to allocate to
> process the hints. The upper limit for this is based on the size of the
> queue used to store the scatterlist.
>
> My primary testing has just been to verify the memory is being freed after
> allocation by running memhog 40g on a 40g guest and watching the total
> free memory via /proc/meminfo on the host. With this I have verified most
> of the memory is freed after each iteration. As far as performance I have
> been mainly focusing on the will-it-scale/page_fault1 test running with
> 16 vcpus. With that I have seen up to a 2% difference between the base
> kernel without these patches and the patches with virtio-balloon enabled
> or disabled.
A couple of questions:
- The 2% difference which you have mentioned, is this visible for
all the 16 cores or just the 16th core?
- I am assuming that the difference is seen for both "number of process"
and "number of threads" launched by page_fault1. Is that right?
>
> One side effect of these patches is that the guest becomes much more
> resilient in terms of NUMA locality. With the pages being freed and then
> reallocated when used it allows for the pages to be much closer to the
> active thread, and as a result there can be situations where this patch
> set will out-perform the stock kernel when the guest memory is not local
> to the guest vCPUs.
Was this the reason because of which you were seeing better results for
page_fault1 earlier?
>
> Patch 4 is a bit on the large side at about 600 lines of change, however
> I really didn't see a good way to break it up since each piece feeds into
> the next. So I couldn't add the statistics by themselves as it didn't
> really make sense to add them without something that will either read or
> increment/decrement them, or add the Hinted state without something that
> would set/unset it. As such I just ended up adding the entire thing as
> one patch. It makes it a bit bigger but avoids the issues in the previous
> set where I was referencing things that had not yet been added.
>
> Changes from the RFC:
> https://lore.kernel.org/lkml/20190530215223.13974.22445.stgit@localhost.localdomain/
> Moved aeration requested flag out of aerator and into zone->flags.
> Moved boundary out of free_area and into local variables for aeration.
> Moved aeration cycle out of interrupt and into workqueue.
> Left nr_free as total pages instead of splitting it between raw and aerated.
> Combined size and physical address values in virtio ring into one 64b value.
>
> Changes from v1:
> https://lore.kernel.org/lkml/20190619222922.1231.27432.stgit@localhost.localdomain/
> Dropped "waste page treatment" in favor of "page hinting"
> Renamed files and functions from "aeration" to "page_hinting"
> Moved from page->lru list to scatterlist
> Replaced wait on refcnt in shutdown with RCU and cancel_delayed_work_sync
> Virtio now uses scatterlist directly instead of intermediate array
> Moved stats out of free_area, now in separate area and pointed to from zone
> Merged patch 5 into patch 4 to improve review-ability
> Updated various code comments throughout
>
> Changes from v2:
> https://lore.kernel.org/lkml/20190724165158.6685.87228.stgit@localhost.localdomain/
> Dropped "page hinting" in favor of "page reporting"
> Renamed files from "hinting" to "reporting"
> Replaced "Hinted" page type with "Reported" page flag
> Added support for page poisoning while hinting is active
> Add QEMU patch that implements PAGE_POISON feature
>
> ---
>
> Alexander Duyck (6):
> mm: Adjust shuffle code to allow for future coalescing
> mm: Move set/get_pcppage_migratetype to mmzone.h
> mm: Use zone and order instead of free area in free_list manipulators
> mm: Introduce Reported pages
> virtio-balloon: Pull page poisoning config out of free page hinting
> virtio-balloon: Add support for providing unused page reports to host
>
>
> drivers/virtio/Kconfig | 1
> drivers/virtio/virtio_balloon.c | 75 ++++++++-
> include/linux/mmzone.h | 116 ++++++++------
> include/linux/page-flags.h | 11 +
> include/linux/page_reporting.h | 138 ++++++++++++++++
> include/uapi/linux/virtio_balloon.h | 1
> mm/Kconfig | 5 +
> mm/Makefile | 1
> mm/internal.h | 18 ++
> mm/memory_hotplug.c | 1
> mm/page_alloc.c | 238 ++++++++++++++++++++--------
> mm/page_reporting.c | 299 +++++++++++++++++++++++++++++++++++
> mm/shuffle.c | 24 ---
> mm/shuffle.h | 32 ++++
> 14 files changed, 821 insertions(+), 139 deletions(-)
> create mode 100644 include/linux/page_reporting.h
> create mode 100644 mm/page_reporting.c
>
> --
>
--
Thanks
Nitesh
next prev parent reply other threads:[~2019-08-02 14:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 22:24 [PATCH v3 0/6] mm / virtio: Provide support for unused page reporting Alexander Duyck
2019-08-01 22:27 ` [PATCH v3 1/6] mm: Adjust shuffle code to allow for future coalescing Alexander Duyck
2019-08-01 22:29 ` [PATCH v3 2/6] mm: Move set/get_pcppage_migratetype to mmzone.h Alexander Duyck
2019-08-01 22:31 ` [PATCH v3 3/6] mm: Use zone and order instead of free area in free_list manipulators Alexander Duyck
2019-08-01 22:33 ` [PATCH v3 4/6] mm: Introduce Reported pages Alexander Duyck
2019-08-05 14:05 ` Nitesh Narayan Lal
2019-08-05 15:11 ` Alexander Duyck
2019-08-01 22:36 ` [PATCH v3 5/6] virtio-balloon: Pull page poisoning config out of free page hinting Alexander Duyck
2019-08-01 22:38 ` [PATCH v3 6/6] virtio-balloon: Add support for providing unused page reports to host Alexander Duyck
2019-08-05 16:00 ` Nitesh Narayan Lal
2019-08-05 16:27 ` Alexander Duyck
2019-08-06 11:31 ` Michael S. Tsirkin
2019-08-06 15:16 ` Alexander Duyck
2019-08-06 15:40 ` Nitesh Narayan Lal
2019-08-01 22:41 ` [PATCH v3 QEMU 1/2] virtio-ballon: Implement support for page poison tracking feature Alexander Duyck
2019-08-01 22:43 ` [PATCH v3 QEMU 2/2] virtio-balloon: Provide a interface for unused page reporting Alexander Duyck
2019-08-02 20:40 ` Nitesh Narayan Lal
2019-08-02 20:58 ` Alexander Duyck
2019-08-02 14:41 ` Nitesh Narayan Lal [this message]
2019-08-02 15:13 ` [PATCH v3 0/6] mm / virtio: Provide support " Alexander Duyck
2019-08-02 16:19 ` Nitesh Narayan Lal
2019-08-02 17:28 ` Alexander Duyck
2019-08-02 23:15 ` Alexander Duyck
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=9cddf98d-e2ce-0f8a-d46c-e15a54bc7391@redhat.com \
--to=nitesh@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.duyck@gmail.com \
--cc=alexander.h.duyck@linux.intel.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=mst@redhat.com \
--cc=pagupta@redhat.com \
--cc=pbonzini@redhat.com \
--cc=riel@surriel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.