From: Daniel Jordan <daniel.m.jordan@oracle.com>
To: Liang Li <liliang.opensource@gmail.com>,
Alexander Duyck <alexander.h.duyck@linux.intel.com>,
Mel Gorman <mgorman@techsingularity.net>,
Andrew Morton <akpm@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Dan Williams <dan.j.williams@intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
David Hildenbrand <david@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Dave Hansen <dave.hansen@intel.com>,
Michal Hocko <mhocko@suse.com>,
Liang Li <liliangleo@didiglobal.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [RFC v2 PATCH 0/4] speed up page allocation for __GFP_ZERO
Date: Tue, 22 Dec 2020 12:11:21 -0500 [thread overview]
Message-ID: <87wnx9rcjq.fsf@oracle.com> (raw)
In-Reply-To: <20201221162519.GA22504@open-light-1.localdomain>
Liang Li <liliang.opensource@gmail.com> writes:
> The first version can be found at: https://lkml.org/lkml/2020/4/12/42
>
> Zero out the page content usually happens when allocating pages with
> the flag of __GFP_ZERO, this is a time consuming operation, it makes
> the population of a large vma area very slowly. This patch introduce
> a new feature for zero out pages before page allocation, it can help
> to speed up page allocation with __GFP_ZERO.
kzeropaged appears to escape some of the kernel's resource controls, at
least if I'm understanding this right.
The heavy part of a page fault is moved out of the faulting task's
context so the CPU controller can't throttle it. A task that uses
these pages can benefit from clearing done by CPUs that it's not allowed
to run on. How can it handle these cases?
next prev parent reply other threads:[~2020-12-22 17:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 16:25 [RFC v2 PATCH 0/4] speed up page allocation for __GFP_ZERO Liang Li
2020-12-22 8:47 ` David Hildenbrand
2020-12-22 11:31 ` Liang Li
2020-12-22 11:57 ` David Hildenbrand
2020-12-22 14:00 ` Liang Li
2020-12-23 8:41 ` David Hildenbrand
2020-12-23 12:11 ` Liang Li
2021-01-04 20:18 ` David Hildenbrand
2021-01-05 2:14 ` Liang Li
2021-01-05 9:39 ` David Hildenbrand
2021-01-05 10:22 ` Liang Li
2021-01-05 10:27 ` David Hildenbrand
2020-12-22 12:23 ` Matthew Wilcox
2020-12-22 14:42 ` Liang Li
2021-01-04 12:51 ` Michal Hocko
2021-01-04 13:45 ` Liang Li
2020-12-22 17:11 ` Daniel Jordan [this message]
2020-12-22 19:13 ` Alexander Duyck
2021-01-04 12:55 ` Michal Hocko
2021-01-04 14:07 ` Liang Li
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=87wnx9rcjq.fsf@oracle.com \
--to=daniel.m.jordan@oracle.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.h.duyck@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=david@redhat.com \
--cc=jasowang@redhat.com \
--cc=liliang.opensource@gmail.com \
--cc=liliangleo@didiglobal.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).