From: Andrew Morton <akpm@linux-foundation.org>
To: Yin Fengwei <fengwei.yin@intel.com>
Cc: linux-mm@kvack.org, willy@infradead.org,
sidhartha.kumar@oracle.com, mike.kravetz@oracle.com,
jane.chu@oracle.com, naoya.horiguchi@nec.com
Subject: Re: [PATCH v2 0/5] batched remove rmap in try_to_unmap_one()
Date: Tue, 28 Feb 2023 12:28:23 -0800 [thread overview]
Message-ID: <20230228122823.eba4f0fa5f7f436a2f8b3a3b@linux-foundation.org> (raw)
In-Reply-To: <20230228122308.2972219-1-fengwei.yin@intel.com>
On Tue, 28 Feb 2023 20:23:03 +0800 Yin Fengwei <fengwei.yin@intel.com> wrote:
> Testing done with the V2 patchset in a qemu guest
> with 4G mem + 512M zram:
> - kernel mm selftest to trigger vmscan() and final hit
> try_to_unmap_one().
> - Inject hwpoison to hugetlb page to trigger try_to_unmap_one()
> call against hugetlb.
> - 8 hours stress testing: Firefox + kernel mm selftest + kernel
> build.
Was any performance testing done with these changes?
next prev parent reply other threads:[~2023-02-28 20:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 12:23 Yin Fengwei
2023-02-28 12:23 ` [PATCH v2 1/5] rmap: move hugetlb try_to_unmap to dedicated function Yin Fengwei
2023-02-28 12:23 ` [PATCH v2 2/5] rmap: move page unmap operation " Yin Fengwei
2023-02-28 12:23 ` [PATCH v2 3/5] rmap: cleanup exit path of try_to_unmap_one_page() Yin Fengwei
2023-02-28 12:23 ` [PATCH v2 4/5] rmap:addd folio_remove_rmap_range() Yin Fengwei
2023-02-28 12:23 ` [PATCH v2 5/5] try_to_unmap_one: batched remove rmap, update folio refcount Yin Fengwei
2023-02-28 20:28 ` Andrew Morton [this message]
2023-03-01 1:44 ` [PATCH v2 0/5] batched remove rmap in try_to_unmap_one() Yin, Fengwei
2023-03-02 10:04 ` David Hildenbrand
2023-03-02 13:32 ` Yin, Fengwei
2023-03-02 14:23 ` David Hildenbrand
2023-03-02 14:33 ` Matthew Wilcox
2023-03-02 14:55 ` David Hildenbrand
2023-03-03 2:44 ` Yin, Fengwei
2023-03-03 2:26 ` Yin, Fengwei
2023-03-06 9:11 ` Yin Fengwei
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=20230228122823.eba4f0fa5f7f436a2f8b3a3b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=fengwei.yin@intel.com \
--cc=jane.chu@oracle.com \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=naoya.horiguchi@nec.com \
--cc=sidhartha.kumar@oracle.com \
--cc=willy@infradead.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