From: Alexander Duyck <alexander.duyck@gmail.com>
To: Gavin Shan <gshan@redhat.com>
Cc: linux-mm <linux-mm@kvack.org>,
David Hildenbrand <david@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
shan.gavin@gmail.com
Subject: Re: [PATCH v3 0/4] mm/page_reporting: Make page reporting work on arm64 with 64KB page size
Date: Tue, 22 Jun 2021 17:52:51 -0700 [thread overview]
Message-ID: <CAKgT0UerGckp0NexSruB2x8EoEwJOVCAgT+x_OooSKwGB2ixJA@mail.gmail.com> (raw)
In-Reply-To: <20210623023418.350616-1-gshan@redhat.com>
So the series looks okay, although I would strongly suggest getting to
work on the virtio_ballon patches to enable reporting the min_order of
the host so that you can override the value in cases where the host is
actually using 512M pages.
For the series:
Reviewed-by: Alexander Duyck <alexanderduyck@fb.com>
On Tue, Jun 22, 2021 at 5:34 PM Gavin Shan <gshan@redhat.com> wrote:
>
> The page reporting threshold is currently equal to @pageblock_order, which
> is 13 and 512MB on arm64 with 64KB base page size selected. The page
> reporting won't be triggered if the freeing page can't come up with a free
> area like that huge. The condition is hard to be met, especially when the
> system memory becomes fragmented.
>
> This series intends to solve the issue by having page reporting threshold
> as 5 (2MB) on arm64 with 64KB base page size. The patches are organized as:
>
> PATCH[1/4] Fix some coding style in __page_reporting_request().
> PATCH[2/4] Represents page reporting order with variable so that it can
> be exported as module parameter.
> PATCH[3/4] Allows the device driver (e.g. virtio_balloon) to specify
> the page reporting order when the device info is registered.
> PATCH[4/4] Specifies the page reporting order to 5, corresponding to
> 2MB in size on ARM64 when 64KB base page size is used.
>
> Changelog
> =========
> v3:
> * Avoid overhead introduced by function all (Alex)
> * Export page reporting order as module parameter (Gavin)
> v2:
> * Rewrite the patches as Alex suggested (Alex)
>
> Gavin Shan (4):
> mm/page_reporting: Fix code style in __page_reporting_request()
> mm/page_reporting: Export reporting order as module parameter
> mm/page_reporting: Allow driver to specify reporting order
> virtio_balloon: Specify page reporting order if needed
>
> Documentation/admin-guide/kernel-parameters.txt | 6 ++++++
> drivers/virtio/virtio_balloon.c | 17 +++++++++++++++++
> include/linux/page_reporting.h | 3 +++
> mm/page_reporting.c | 16 ++++++++++++----
> mm/page_reporting.h | 5 ++---
> 5 files changed, 40 insertions(+), 7 deletions(-)
>
> --
> 2.23.0
>
next prev parent reply other threads:[~2021-06-23 0:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 2:34 Gavin Shan
2021-06-23 0:52 ` Alexander Duyck [this message]
2021-06-23 2:34 ` [PATCH v3 1/4] mm/page_reporting: Fix code style in __page_reporting_request() Gavin Shan
2021-06-23 2:34 ` [PATCH v3 2/4] mm/page_reporting: Export reporting order as module parameter Gavin Shan
2021-06-24 13:55 ` Alexander Duyck
2021-06-24 19:02 ` Michael S. Tsirkin
2021-06-25 1:54 ` Gavin Shan
2021-06-23 2:34 ` [PATCH v3 3/4] mm/page_reporting: Allow driver to specify reporting order Gavin Shan
2021-06-23 2:34 ` [PATCH v3 4/4] virtio_balloon: Specify page reporting order if needed Gavin Shan
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=CAKgT0UerGckp0NexSruB2x8EoEwJOVCAgT+x_OooSKwGB2ixJA@mail.gmail.com \
--to=alexander.duyck@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=gshan@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mst@redhat.com \
--cc=shan.gavin@gmail.com \
--cc=will@kernel.org \
/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