From: Liang Li <liliang324@gmail.com>
To: Michal Hocko <mhocko@suse.com>
Cc: 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>,
Liang Li <liliangleo@didiglobal.com>,
linux-mm <linux-mm@kvack.org>,
LKML <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: Mon, 4 Jan 2021 22:07:05 +0800 [thread overview]
Message-ID: <CA+2MQi9iViYq7+apaJEymt8rZxUuo+9EJN4x3_RRydjr7-vwMQ@mail.gmail.com> (raw)
In-Reply-To: <20210104125554.GE13207@dhcp22.suse.cz>
On Mon, Jan 4, 2021 at 8:56 PM Michal Hocko <mhocko@suse.com> wrote:
>
> On Mon 21-12-20 11:25:22, Liang Li wrote:
> [...]
> > Security
> > ========
> > This is a weak version of "introduce init_on_alloc=1 and init_on_free=1
> > boot options", which zero out page in a asynchronous way. For users can't
> > tolerate the impaction of 'init_on_alloc=1' or 'init_on_free=1' brings,
> > this feauture provide another choice.
>
> Most of the usecases are about the start up time imporvemtns IIUC. Have
> you tried to use init_on_free or this would be prohibitive for your
> workloads?
>
I have not tried yet. 'init_on_free' may help to shorten the start up time. In
our use case, we care about both the VM creation time and the VM reboot
time[terminate QEMU process first and launch a new one], 'init_on_free'
will slow down the termination process and is not helpful for VM reboot.
Our aim is to speed up 'VM start up' and not slow down 'VM shut down'.
Thanks
Liang
next prev parent reply other threads:[~2021-01-04 14:08 UTC|newest]
Thread overview: 37+ 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 8:47 ` David Hildenbrand
2020-12-22 11:31 ` Liang Li
2020-12-22 11:31 ` Liang Li
2020-12-22 11:57 ` David Hildenbrand
2020-12-22 11:57 ` David Hildenbrand
2020-12-22 14:00 ` Liang Li
2020-12-22 14:00 ` Liang Li
2020-12-23 8:41 ` David Hildenbrand
2020-12-23 8:41 ` David Hildenbrand
2020-12-23 12:11 ` Liang Li
2020-12-23 12:11 ` Liang Li
2021-01-04 20:18 ` David Hildenbrand
2021-01-04 20:18 ` David Hildenbrand
2021-01-05 2:14 ` Liang Li
2021-01-05 2:14 ` Liang Li
2021-01-05 9:39 ` David Hildenbrand
2021-01-05 9:39 ` David Hildenbrand
2021-01-05 10:22 ` Liang Li
2021-01-05 10:22 ` Liang Li
2021-01-05 10:27 ` David Hildenbrand
2021-01-05 10:27 ` David Hildenbrand
2020-12-22 12:23 ` Matthew Wilcox
2020-12-22 12:23 ` Matthew Wilcox
2020-12-22 14:42 ` Liang Li
2020-12-22 14:42 ` Liang Li
2021-01-04 12:51 ` Michal Hocko
2021-01-04 13:45 ` Liang Li
2021-01-04 13:45 ` Liang Li
2020-12-22 17:11 ` Daniel Jordan
2020-12-22 19:13 ` Alexander Duyck
2020-12-22 19:13 ` Alexander Duyck
2020-12-22 19:13 ` Alexander Duyck
2021-01-04 12:55 ` Michal Hocko
2021-01-04 14:07 ` Liang Li [this message]
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=CA+2MQi9iViYq7+apaJEymt8rZxUuo+9EJN4x3_RRydjr7-vwMQ@mail.gmail.com \
--to=liliang324@gmail.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 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.