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 Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 10370C77B77 for ; Mon, 17 Apr 2023 07:37:48 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 8D01C8E0002; Mon, 17 Apr 2023 03:37:47 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 87F848E0001; Mon, 17 Apr 2023 03:37:47 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 7473F8E0002; Mon, 17 Apr 2023 03:37:47 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0014.hostedemail.com [216.40.44.14]) by kanga.kvack.org (Postfix) with ESMTP id 62AB88E0001 for ; Mon, 17 Apr 2023 03:37:47 -0400 (EDT) Received: from smtpin27.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay03.hostedemail.com (Postfix) with ESMTP id 2DCBDA034E for ; Mon, 17 Apr 2023 07:37:47 +0000 (UTC) X-FDA: 80690078574.27.5F36DC6 Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by imf28.hostedemail.com (Postfix) with ESMTP id 22778C0003 for ; Mon, 17 Apr 2023 07:37:44 +0000 (UTC) Authentication-Results: imf28.hostedemail.com; dkim=pass header.d=suse.cz header.s=susede2_rsa header.b=FSNHYP0e; dkim=pass header.d=suse.cz header.s=susede2_ed25519 header.b=InpvAvPh; spf=pass (imf28.hostedemail.com: domain of vbabka@suse.cz designates 195.135.220.28 as permitted sender) smtp.mailfrom=vbabka@suse.cz; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1681717065; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=3w8ZyhKSUCHQYqIG32tqYuuJnDNxaXTVQggusp/+GOc=; b=T7EPpHwcSMyy7qFxDDlmvbQVMgSAakvykiiGWXsWmCknHoisf7HN/Rj1vloA1rG3YBqDXI OmwHGJxFwCn6OPd9sXPlOAedLZLNW6FU1plzVz3ul1NdJ1mFzDYP+VZZOA9IxP0UfUfxeR m+ojHrr+JTc/eaUUz823RH5B3e/hMaU= ARC-Authentication-Results: i=1; imf28.hostedemail.com; dkim=pass header.d=suse.cz header.s=susede2_rsa header.b=FSNHYP0e; dkim=pass header.d=suse.cz header.s=susede2_ed25519 header.b=InpvAvPh; spf=pass (imf28.hostedemail.com: domain of vbabka@suse.cz designates 195.135.220.28 as permitted sender) smtp.mailfrom=vbabka@suse.cz; dmarc=none ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1681717065; a=rsa-sha256; cv=none; b=5RzyMwGG1KzXsy2p3ijtvUAH9s1zV5iM9XL9FJQl4YK5L4SDbo+o6hwQSy/Bvf7emtM6+5 BfOjsN+XEuQbuXSGO4kAwoiSQBJmqYiDBHh5CxLajb0uoLpXwVgaTJZbQc3zAORg+zQ7us QYxX9e6YPb989cKZh00I30KwxrGfI2s= Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 53B2C21A3D; Mon, 17 Apr 2023 07:37:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1681717063; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=3w8ZyhKSUCHQYqIG32tqYuuJnDNxaXTVQggusp/+GOc=; b=FSNHYP0e1N/1O21SR61SdobJRwQUe/xR/QsGmyhBrzM3xQ9/FqLwkxXkORxQN3bPPepVvC J1AJE4vC95OYz9443C58v7MQnRLUKXQ9f+JVSbGagwIxrFIZl66nsCBIWd0BpRiHdw+A/Z BggQEkAKglbqgPoTFhbrqFUgWHIAdzs= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1681717063; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=3w8ZyhKSUCHQYqIG32tqYuuJnDNxaXTVQggusp/+GOc=; b=InpvAvPhIJbDcKWUuYK6TRVNdy9BaqeoAVEyr3zLiU0ZyYIRJ1A/+0gB/YuJNZValGrWhk +iHsclhRxLILHaAA== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id B5DC61390E; Mon, 17 Apr 2023 07:37:42 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id 5jMCK0b3PGQjJQAAMHmgww (envelope-from ); Mon, 17 Apr 2023 07:37:42 +0000 Message-ID: Date: Mon, 17 Apr 2023 09:37:42 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0 Subject: Re: [PATCHv9 00/14] mm, x86/cc: Implement support for unaccepted memory Content-Language: en-US To: "Kirill A. Shutemov" Cc: "Kirill A. Shutemov" , Borislav Petkov , Andy Lutomirski , Sean Christopherson , Andrew Morton , Joerg Roedel , Ard Biesheuvel , Andi Kleen , Kuppuswamy Sathyanarayanan , David Rientjes , Tom Lendacky , Thomas Gleixner , Peter Zijlstra , Paolo Bonzini , Ingo Molnar , Dario Faggioli , Dave Hansen , Mike Rapoport , David Hildenbrand , Mel Gorman , marcelo.cerri@canonical.com, tim.gardner@canonical.com, khalid.elmously@canonical.com, philip.cox@canonical.com, aarcange@redhat.com, peterx@redhat.com, x86@kernel.org, linux-mm@kvack.org, linux-coco@lists.linux.dev, linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org References: <20230330114956.20342-1-kirill.shutemov@linux.intel.com> <2e0da486-71e4-cfeb-1578-68f1c8c43d33@suse.cz> <20230416191940.ex7ao43pmrjhru2p@box.shutemov.name> From: Vlastimil Babka In-Reply-To: <20230416191940.ex7ao43pmrjhru2p@box.shutemov.name> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 22778C0003 X-Stat-Signature: jeub4ece651fk9b5r4r3u1ynj5xqn3i4 X-Rspam-User: X-Rspamd-Server: rspam08 X-HE-Tag: 1681717064-578396 X-HE-Meta: U2FsdGVkX1+4cBttaySqMpuxCPOzL1ouApdeLZhua2aZK6Vzo5f9EXaE0ZokkgnayNkPdFzo+GBfUFJ7TQI/vdf7J4CieMZU7v0lIKEnv61WcPY3E7GWkQsYIr38iY1WBVbYtyqbQOyCJdNzh0OrkyuPYoXXWFmPrgMNsQ5KNmyY/lByDuND7WlihxlilYmPvzAtYceeWdUKzB78NJzRwJjF5CCdvHMwwzDLqxLA2nO9PtmkQeRA/rp0UgE7pRaMkUSJQp+PZlsNzqAw7D/IH4Hc30HZRJ/aFRArKZR+OmMHOpNPBDsU/QjVIBOhiuyB9X6vXsIzwKJ2qqTqQHraC5YH3+lQDimPzw6h7xjEzlN8EPvo3V0/BG9KyfweMLcwAa6u4FDjTifGJTvvdLb7tjr0XQULo+PIZ6dt5a0+ZJrk1Qoo/TMA1KCVkGK+X1rzqOqw7itZGIPch2b3HEjFXcbJXLCXnuAcQwOzgNxDJtvCgW6aDBhj5JgX9CWh2cprb76c6BEobGq8pq1lWkkoJ+4Juo9FjyQMqvxUj8IjAJF8zaw5TrOYEfuCKrO0mH4JjffVwNoelOfFORpV0sZQhE5DpbZ8Ft/pwnw+zKwhwCjFrEKrePXS3snoyN0sEiSH1NBEF+zoCxj7gd7BKt4Xq7YOceoyKbVHNkqL2Ld3DpywEdOSFe8cts1MEN7GW6wn5z/MdrgxAU6C4MYOGCOjBHMvNijrMJr7i7een6QXaRPe3QClHPBV197VoL66YOZE5kCjSLWXmRg5YUWMQ1V6llZ+9Uqt1LsC3eIbW1Uh9fxoixdTuGZMELH0d0kSDM8PsQoPzPd51xihyJHjXx9XScl0BFFZAMMlDDoYxuHUIHy96bKOcwEm4blAK440n2DMx/TVk6k1B2z6QrgtxOj6MsvJFNM1j3BZ5FsjaDgNKo52STTznhGA+ccEVeYlpHVNEAVexkgYUm028Wf1kTV WxJrPkgI yMhHpHMvW9d2ohozf2x/g/+TedkcpG0KCeLu7ywxZ9ZpMbD4b18et5cE41WjbxzGQYBBZId/ni6c6H+RUbRGg1fSk8jwItct93FodngFeDE36BaZwiuejwnlEt09KUeLb4VtBy7uJMTMA5z2EGhbYZYq4r6fmyPseve6PuMxhpEH6YGIIYzdYPGHBazS8msizVi9yvESJfIY34gxTEZslY/w0zQ== 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 4/16/23 21:19, Kirill A. Shutemov wrote: > On Mon, Apr 03, 2023 at 04:42:54PM +0200, Vlastimil Babka wrote: >> Hmm yeah it can be noisy. Did you try to only count events that have >> fragmenting=1 and/or MIGRATE_MOVABLE as fallback_migratetype? As those are >> the really bad events. > > I finally got around to retest it. > > total fragmenting movable fragmenting&&movable > base-1: 957 583 353 0 > base-2: 2715 2343 359 0 > base-3: 2033 1669 353 0 > patched-1: 1325 929 371 0 > patched-2: 2844 2451 371 0 > patched-3: 1304 917 361 0 > > fragmenting=1 is defined as fallback_order of them. > > Patched kernel showed slightly elevated movable(fallback_migratetype=1) > cases. Is it critical? Maybe it's still not statistically significant anyway, also not as cricical as fragmenting&movable. > There's no allocations that is fragmenting and movable. Hm. It probably means your test wasn't stressfull enough to inflict a mix of rapid movable an unmovable allocations when memory is nearly full. But at that point the memory is all accepted, so we don't need such scenario. The important thing is that this kind of events didn't start happening during the gradual memory accepting phase.