From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.4 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DFFA6C55179 for ; Tue, 27 Oct 2020 11:05:25 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 3FB6521655 for ; Tue, 27 Oct 2020 11:05:24 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3FB6521655 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.cz Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 6433B6B006E; Tue, 27 Oct 2020 07:05:24 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 5F5056B0070; Tue, 27 Oct 2020 07:05:24 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 50C966B0071; Tue, 27 Oct 2020 07:05:24 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0071.hostedemail.com [216.40.44.71]) by kanga.kvack.org (Postfix) with ESMTP id 247A86B006E for ; Tue, 27 Oct 2020 07:05:24 -0400 (EDT) Received: from smtpin04.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id C07E2180AD804 for ; Tue, 27 Oct 2020 11:05:23 +0000 (UTC) X-FDA: 77417424126.04.mouth04_420ad852727b Received: from filter.hostedemail.com (10.5.16.251.rfc1918.com [10.5.16.251]) by smtpin04.hostedemail.com (Postfix) with ESMTP id A44728006983 for ; Tue, 27 Oct 2020 11:05:23 +0000 (UTC) X-HE-Tag: mouth04_420ad852727b X-Filterd-Recvd-Size: 2954 Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by imf48.hostedemail.com (Postfix) with ESMTP for ; Tue, 27 Oct 2020 11:05:23 +0000 (UTC) X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id A7CD1AAF1; Tue, 27 Oct 2020 11:05:21 +0000 (UTC) To: David Hildenbrand , Andrew Morton Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Alexander Potapenko , Kees Cook , Michal Hocko , Mateusz Nosek References: <20201026173358.14704-1-vbabka@suse.cz> <20201026173358.14704-4-vbabka@suse.cz> <93ab79df-cf8c-294b-3ed1-8a563e4a452b@redhat.com> From: Vlastimil Babka Subject: Re: [PATCH 3/3] mm, page_alloc: reduce static keys in prep_new_page() Message-ID: <1fc7ec3a-367c-eb9f-1cb4-b9e015fea87c@suse.cz> Date: Tue, 27 Oct 2020 12:05:21 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.3.3 MIME-Version: 1.0 In-Reply-To: <93ab79df-cf8c-294b-3ed1-8a563e4a452b@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 10/27/20 10:10 AM, David Hildenbrand wrote: > On 26.10.20 18:33, Vlastimil Babka wrote: >> prep_new_page() will always zero a new page (regardless of __GFP_ZERO)= when >> init_on_alloc is enabled, but will also always skip zeroing if the pag= e was >> already zeroed on free by init_on_free or page poisoning. >>=20 >> The latter check implemented by free_pages_prezeroed() can involve two >> different static keys. As prep_new_page() is really a hot path, let's = introduce >> a single static key free_pages_not_prezeroed for this purpose and init= ialize it >> in init_mem_debugging(). >=20 > Is this actually observable in practice? This smells like > micro-optimization to me. >=20 > Also, I thought the whole reason for static keys is to have basically n= o > overhead at runtime, so I wonder if replacing two static key checks by = a > single one actually makes *some* difference. You're right, the difference seems to be just a single NOP. The static ke= y=20 infrastructure seems to be working really well. (At least the asm inspection made me realize that kernel_poison_pages() i= s=20 called unconditionally and the static key is checked inside, not inline s= o I'll=20 be amending patch 2...) Initially I thought I would be reducing 3 keys to 1 in this patch, but I = got the=20 code wrong. So unless others think it's a readability improvements, we ca= n drop=20 this patch. Or we can also reconsider this whole optimization. If the point is to be=20 paranoid and enable both init_on_free and init_on_alloc, should we trust = that=20 nobody wrote something after the clearing on free via use-after-free? :) = Kees/Alex?