Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp743155ybz; Wed, 22 Apr 2020 07:14:07 -0700 (PDT) X-Google-Smtp-Source: APiQypJ6IDLlXvQPrX4gjedxJCPBwKeSaQk1A+2vUixnCvzGNvISQRrEtHJqJXB6qD+xBNFDSY10 X-Received: by 2002:a17:906:31da:: with SMTP id f26mr19722097ejf.308.1587564847641; Wed, 22 Apr 2020 07:14:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587564847; cv=none; d=google.com; s=arc-20160816; b=ZuCdmr2736dSFylVfgl0LS06PEDkfcS1KxYC2P3kSXb15mKk/3vjeDwv40n7FJtI2y P58eojyenOZZNCBwsbRxiRIwyBCL3Z57IZtLgRZN2v1rUlakK5D2ToqwePOVpsL5G7SE He5W7Yfj1+37WYCd6KZ56jbSvOXx6krlFQGX3BLii9G37ZJPaK8r/BbsAhuXuOl/DcVA wqhzA+YsYKQDgceXBATRb8za1xDFl8vDqf92UguLHLUFVDEoOCwL3mn5S84zoQ/Gj9ra IqZ4jw3I87GI7Mkvz5XnJsWCDWH+nYQaQfkuCKd4orJwpHI/Al9A3RRk54LOTOhNaxDa ysnQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=+kXHM5vyTYke7NZ+riTm1fdcuRfAUdxDhoaheebL1YM=; b=g10qbz4FLNTlNEfufIl0+4t08+o7FKlzHt7JaC2EqAjfVMLL8AVQ+BYmEeybaW0vQy 6vO0iZMsupGPnzvC5DFODktvujxFYZM3r/Prk25l8CbtBzSaWTgClkNAFeA1NTLlkTwa SqOxVl3JnScOdlBJWNISRl6XzBz1lX5WNFtM0IvetfYruHBWrJGsB/ovg5Z1mjA5A1b9 XKLakaYtxVZArVPWNHIhJGb7pUTvTyOZM6lxnEcagJvpBO3dxZBCEh4Le3rOciWqaNmS NcUPcJu+qO7bWPr8BDRqhTxhRoYpHQROZebaK/HxAjn/PXH96RUdqcJMY3B5fPRla+NY 6bDA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a4si3637516edn.451.2020.04.22.07.13.34; Wed, 22 Apr 2020 07:14:07 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727075AbgDVOJG (ORCPT + 99 others); Wed, 22 Apr 2020 10:09:06 -0400 Received: from mx2.suse.de ([195.135.220.15]:59046 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725810AbgDVOJF (ORCPT ); Wed, 22 Apr 2020 10:09:05 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 817B3ABCF; Wed, 22 Apr 2020 14:09:02 +0000 (UTC) Subject: Re: [RFC PATCH 4/4] mm: Add PG_zero support To: Andrew Morton , Alexander Duyck Cc: Matthew Wilcox , Mel Gorman , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Andrea Arcangeli , Dan Williams , Dave Hansen , David Hildenbrand , Michal Hocko , Alex Williamson References: <20200412090945.GA19582@open-light-1.localdomain> <20200412101223.GK21484@bombadil.infradead.org> <5eb37d79-6420-fcb9-2b4c-6cc6194afcd9@linux.intel.com> <20200413140537.eb674579cf8c71b4e20581ab@linux-foundation.org> From: Vlastimil Babka Message-ID: <344a3a78-62ad-48fe-40cf-18993175d1e0@suse.cz> Date: Wed, 22 Apr 2020 16:09:00 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <20200413140537.eb674579cf8c71b4e20581ab@linux-foundation.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/13/20 11:05 PM, Andrew Morton wrote: > On Mon, 13 Apr 2020 08:11:59 -0700 Alexander Duyck wrote: > >> In addition, unlike madvising the page away there is a pretty >> significant performance penalty for having to clear the page a second >> time when the page is split or merged. > > I wonder if there might be an issue with increased memory traffic (and > increased energy consumption, etc). If a page is zeroed immediately > before getting data written into it (eg, plain old file write(), > anonymous pagefault) then we can expect that those 4096 zeroes will be > in CPU cache and mostly not written back. But if that page was zeroed > a "long" time ago, the caches will probably have been written back. > Net result: we go from 4k of memory traffic for a 4k page up to 8k of > memory traffic? Heh, I was quite sure that this is not the first time background zeroing is proposed, so I went to google for it... and found that one BSD kernel actually removed this functionality in 2016 [1] and this was one of the reasons. [1] https://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/afd2da4dc9056ea79cdf15e8a9386a3d3998f33e > Also, the name CONFIG_ZERO_PAGE sounds like it has something to do with > the long established "zero page". Confusing. CONFIG_PREZERO_PAGE, > maybe? >