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 87D34EB64DA for ; Thu, 6 Jul 2023 00:24:31 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id AD8798D0002; Wed, 5 Jul 2023 20:24:30 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id A88D98D0001; Wed, 5 Jul 2023 20:24:30 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 950658D0002; Wed, 5 Jul 2023 20:24:30 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0010.hostedemail.com [216.40.44.10]) by kanga.kvack.org (Postfix) with ESMTP id 863BF8D0001 for ; Wed, 5 Jul 2023 20:24:30 -0400 (EDT) Received: from smtpin30.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay03.hostedemail.com (Postfix) with ESMTP id 53C05A05F9 for ; Thu, 6 Jul 2023 00:24:30 +0000 (UTC) X-FDA: 80979290700.30.8903779 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by imf05.hostedemail.com (Postfix) with ESMTP id 85C97100019 for ; Thu, 6 Jul 2023 00:24:28 +0000 (UTC) Authentication-Results: imf05.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=korg header.b=yLKdaY+X; spf=pass (imf05.hostedemail.com: domain of akpm@linux-foundation.org designates 139.178.84.217 as permitted sender) smtp.mailfrom=akpm@linux-foundation.org; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1688603068; 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=dLyKsT+kapG0zXb6Tn2fU9Q1SIeSEUpg2tcLvn9UuIk=; b=daD3T3sDkytG/L6KTzoYuweIdw1RDEPYDBBYw70h8NUsNyXaBhKMPh2IrUnPnzlFnQHg7l 9SWGemNpJ6UkTAdKGQUBiXyQPL+YXnc4z23LVWr2vOFQPGlFfVMeVCwtaIL9bdPDfQtgaj dxs51DsX30G0f7NbuxlX2zCiI2fdZYw= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1688603068; a=rsa-sha256; cv=none; b=gmecl+Yab1mlif49h0O2YOO5ZRirb1QtNjVnhII8d1EXZti6/xDa1togW8NHncHdZS/SoH AjjxVVxLT9uKEZght+JUHqX3GokcoAKfapJLDg3ZJ+U9tMaYNIlqCi3OAKUZDcS/Br6dDc oZ/h/pMX68Fe6resopg5B8I24LRYjdQ= ARC-Authentication-Results: i=1; imf05.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=korg header.b=yLKdaY+X; spf=pass (imf05.hostedemail.com: domain of akpm@linux-foundation.org designates 139.178.84.217 as permitted sender) smtp.mailfrom=akpm@linux-foundation.org; dmarc=none Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 7B55D6144C; Thu, 6 Jul 2023 00:24:27 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 507C7C433C7; Thu, 6 Jul 2023 00:24:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1688603066; bh=nHq1jiHWn2nbRo9u6c10UMyjMbeMQ1kawY7UenaWBCk=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=yLKdaY+XITYZVKJXLiB+qldsxMsM9l3kbopRLz2Yq90xxJBO0YUKqfOz55dfw9wID rE7bWso6GjqPFLa9FdDOu6gFdMUD5HPTH1kY0kOhw5PKMCAh3amACOkx1WnvjTn82M p0pTkTNSDQuNfNi7X78fO4bxYKWJ6NO+W+XVbNug= Date: Wed, 5 Jul 2023 17:24:24 -0700 From: Andrew Morton To: Suren Baghdasaryan Cc: Peter Xu , David Hildenbrand , jirislaby@kernel.org, jacobly.alt@gmail.com, holger@applied-asynchrony.com, hdegoede@redhat.com, michel@lespinasse.org, jglisse@google.com, mhocko@suse.com, vbabka@suse.cz, hannes@cmpxchg.org, mgorman@techsingularity.net, dave@stgolabs.net, willy@infradead.org, liam.howlett@oracle.com, peterz@infradead.org, ldufour@linux.ibm.com, paulmck@kernel.org, mingo@redhat.com, will@kernel.org, luto@kernel.org, songliubraving@fb.com, dhowells@redhat.com, hughd@google.com, bigeasy@linutronix.de, kent.overstreet@linux.dev, punit.agrawal@bytedance.com, lstoakes@gmail.com, peterjung1337@gmail.com, rientjes@google.com, chriscli@google.com, axelrasmussen@google.com, joelaf@google.com, minchan@google.com, rppt@kernel.org, jannh@google.com, shakeelb@google.com, tatashin@google.com, edumazet@google.com, gthelen@google.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH v3 2/2] mm: disable CONFIG_PER_VMA_LOCK until its fixed Message-Id: <20230705172424.e505f5013bfdf44543d9c6be@linux-foundation.org> In-Reply-To: References: <20230705171213.2843068-1-surenb@google.com> <20230705171213.2843068-3-surenb@google.com> <3cdaa7d4-1293-3806-05ce-6b7fc4382458@redhat.com> X-Mailer: Sylpheed 3.8.0beta1 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 85C97100019 X-Rspam-User: X-Rspamd-Server: rspam11 X-Stat-Signature: uqmymjsiso3iuuexi5dqzk9q7sswky8u X-HE-Tag: 1688603068-736796 X-HE-Meta: U2FsdGVkX1/xiQprI3hEmG9v7W7/2+Kh3LatLyQgYMWfV+C8gUB6x13ddQyPVReXM5thxVSfHLBzrHWfuz7i1H6NdLy8qxPBMH3M7CuvYx2cT2hrYKr03kxNSZD1qkr271a9BKF81PbgaYP3wtAR6s0wPZLk7o4qWzv9UcflzlS7cHYjzncAQ1tBf6JdDarMVG7qhVT8Aq6gnrVhTiAB44NpuU0I93fEye3HH+7xhP0QJxo6gBwP84mgY8thU4smB1SEq60PutiwGFpLoNqcTEw1NOH8XGEBKjyKq3vOCyLoKX2IdU2T7ko2Vp2U/ImRSHJeO4rF5y+3pSEY9bx05SekAtTtx87ivg3bfX/HQqgn8u/otRFi+IVPySOge85mtab9Q4mjXyvW3y0mtusmcTAxrmvm/rmbynJwzjwFml+vk4IajRNZwklnZnAo7FCDKgMmjezCQlOPcII9i/8eOvQWPoMozdtZB8z1LdRxvvgklrRC7FjfDo9or5byXqkUC6ALJGT0Axp38vCReH8Q2bzsTWCoAtUFTxO/GyA/tU9sCs/5UzDIDGpNE+4rQfTCBeIuZWhokROEmQgwQUJZh/Ye27Qyq2VO2lc6m9bBHxISmGJgmXv5RamTDPl7Non8YjRjOBVdb3UmoxA1/0wV1+jGE4xVdGwBduoMhnyGEfj/Yqa5ODo1OGNShgmWklA9+pK1Ozq43+uSo3hpsrOoVpANWmzCNtWUYGyFspFsbn1WM5Sl7O+337ZHpwdUWOynXA3brZ/9eak1xCYaONQzi8U5IxryyZpwdCW1hngK+418Bs6HDTGDVYNJAodTG4lkBxiyKYIQf7vu8BzsyWBTiXVtS9t9Fm4RVeJt+qyrsCaSThsnY7Ll45f7EivmJU0mdvgvpSc7L6Nk8clrB6hH2XOx3vjVUOAowRwt7UJXP3YnXw9mggwOTcuJZeV5VnKwjEH+L0hbhju0B+ZFwtF tc9LKGUg EUQC64KpuvGOo9wynXG5UP0g2UTiEbEx6qrEmAMxdqRHEOk/+5Senu76LnePJhBUswTotQolKpXDvV0NrRDbp7KYB0MZ9wh7UZzRj2hyLOw8lWMlj8zX1S2MfWI0UQtw0mwzQ0SdtTMFF/hIDfBtYphoTFDZ7Aaf81M8V6PtvnBVfPOU+6LkTLkNAWuPjEAGbl+aDNavWoNxwEVnZiDXXbkFlzrUtVhtkF7YoOj47SBaIdgverKiEZ60PNDXr27cUsfxPVMljugguSllkFmU8gtv6z3KPXsbzUugEGDd6AeXMdwe0rwjDSEodNX/oGb51ILCg9OUhnmBxBJiuCOMJX0uBeFl1bRsW4qP+z3sqD2KoCoN0brC/Ep7RUKuMAWQPvBzW+4DurX5gtQhlQgXPGvdl7HykKq4t5fnyiHG4BrmAcoEQpyWdhHj2T8h0MUYW0oOcxb4JWlBDZLB/IlbFzHPmfE68wX4X75d9JknRLvJScs+VPWeLqEk5Vw== 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 Wed, 5 Jul 2023 13:33:26 -0700 Suren Baghdasaryan wrote: > I was hoping we could re-enable VMA locks in 6.4 once we get more > confirmations that the problem is gone. Is that not possible once the > BROKEN dependency is merged? I think "no". By doing this we're effectively backporting a minor performance optimization, which isn't a thing we'd normally do.