[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210105095621.GB13207@dhcp22.suse.cz>
Date: Tue, 5 Jan 2021 10:56:21 +0100
From: Michal Hocko <mhocko@...e.com>
To: David Hildenbrand <david@...hat.com>
Cc: Dave Hansen <dave.hansen@...el.com>,
Matthew Wilcox <willy@...radead.org>,
Alexander Duyck <alexander.h.duyck@...ux.intel.com>,
Mel Gorman <mgorman@...hsingularity.net>,
Andrew Morton <akpm@...ux-foundation.org>,
Andrea Arcangeli <aarcange@...hat.com>,
Dan Williams <dan.j.williams@...el.com>,
"Michael S. Tsirkin" <mst@...hat.com>,
Jason Wang <jasowang@...hat.com>,
Liang Li <liliangleo@...iglobal.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org
Subject: Re: [RFC v2 PATCH 4/4] mm: pre zero out free pages to speed up page
allocation for __GFP_ZERO
On Tue 05-01-21 10:29:45, David Hildenbrand wrote:
> On 05.01.21 10:20, Michal Hocko wrote:
[...]
> > A global knob with all or nothing sounds like an easier to use and
> > maintain solution to me.
>
> I mean, that brings me back to my original suggestion: just use
> hugetlbfs and implement some sort of pre-zeroing there (worker thread,
> whatsoever). Most vfio users should already be better of using hugepages.
Shifting background zeroying to hugetlb would solve the problem with the
work accounting, right? Somebody has to pay for that work and piggy back
on all other CPU consumers by default is not acceptable even when that
is reduced to hugetlb.
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists