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 0B23EC43334 for ; Thu, 16 Jun 2022 16:54:17 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 90CD16B0072; Thu, 16 Jun 2022 12:54:16 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 8957F6B0074; Thu, 16 Jun 2022 12:54:16 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 6E7B96B0075; Thu, 16 Jun 2022 12:54:16 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0017.hostedemail.com [216.40.44.17]) by kanga.kvack.org (Postfix) with ESMTP id 5C06D6B0072 for ; Thu, 16 Jun 2022 12:54:16 -0400 (EDT) Received: from smtpin11.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay10.hostedemail.com (Postfix) with ESMTP id 2E9F7532 for ; Thu, 16 Jun 2022 16:54:16 +0000 (UTC) X-FDA: 79584696912.11.E60C0F9 Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by imf18.hostedemail.com (Postfix) with ESMTP id 364E81C0074 for ; Thu, 16 Jun 2022 16:54:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1655398454; x=1686934454; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=lqAjFaMd+IIDWYQLfoAerUJeGKE/DpmPQXkgkytknlI=; b=AkD5Kc6UZM+HDptVDynELa2eVHRsQ6XEA61+yqf1tNKL7SmsKrgX+scn KYwx8FS3fkVKvGmC7fzHqsjTSRZJO2Bvyuio585oQhvOtOroxvaX20uA5 Eg0OjY5jdn6GMruFpfRiC1dQU8803/wAV137Y59ysZWNmHQzT7Tiz0u0k E4oTu948Lwj5P9HNX44NDD1EIvErfh3AD8Qi17oP0yFAQgA14ROp8KmJy LZv9wWjnMOWx5tKJU9k1k3wBAivTk6ql48DuNMSD3hi+dbhWryg8C1tuS nI37cIK1CFGV22extnQOrrNJakxWUGwDqAd4QT00Ca/n9kiOW78fo0Ms2 A==; X-IronPort-AV: E=McAfee;i="6400,9594,10380"; a="262314703" X-IronPort-AV: E=Sophos;i="5.92,305,1650956400"; d="scan'208";a="262314703" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Jun 2022 09:54:12 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.92,305,1650956400"; d="scan'208";a="912238632" Received: from black.fi.intel.com ([10.237.72.28]) by fmsmga005.fm.intel.com with ESMTP; 16 Jun 2022 09:54:09 -0700 Received: by black.fi.intel.com (Postfix, from userid 1000) id 95605109; Thu, 16 Jun 2022 19:54:13 +0300 (EEST) Date: Thu, 16 Jun 2022 19:54:13 +0300 From: "Kirill A. Shutemov" To: Peter Zijlstra Cc: Andy Lutomirski , Rick P Edgecombe , Linux Kernel Mailing List , "H.J. Lu" , "linux-mm@kvack.org" , Dave Hansen , "andreyknvl@gmail.com" , "kcc@google.com" , Andi Kleen , "dvyukov@google.com" , the arch/x86 maintainers , "ryabinin.a.a@gmail.com" , "glider@google.com" Subject: Re: [PATCHv3 6/8] x86/mm: Provide ARCH_GET_UNTAG_MASK and ARCH_ENABLE_TAGGED_ADDR Message-ID: <20220616165413.c35yliaxbxvmwsqw@black.fi.intel.com> References: <20220610143527.22974-1-kirill.shutemov@linux.intel.com> <20220610143527.22974-7-kirill.shutemov@linux.intel.com> <20220610180635.l44opq2votd3gxpl@black.fi.intel.com> <5b56c88e477d879e5a0e3c15627cb05901a812f4.camel@intel.com> <5d3b281f-3d8b-4bbd-9681-b226810c3e8b@www.fastmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1655398454; a=rsa-sha256; cv=none; b=2EparxCe5WzEA5eiSvITK88M7MPXC7FjP9AecPT6/fhk94vN3KzfXBZOjz6NjEtDpFW48D w1Qufs4rrq7YQX4xjUX2wYdNxb+69HF2oBvXmYKGoU2x7BPlC3e9TYXiAYoyUV7Kvb1eGo mQhQVzVWdj0dB1sYzK0NF79Ta/AMW5s= ARC-Authentication-Results: i=1; imf18.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=AkD5Kc6U; spf=none (imf18.hostedemail.com: domain of kirill.shutemov@linux.intel.com has no SPF policy when checking 134.134.136.126) smtp.mailfrom=kirill.shutemov@linux.intel.com; dmarc=pass (policy=none) header.from=intel.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1655398454; 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: in-reply-to:in-reply-to:references:references:dkim-signature; bh=8o8VvYP2cWyl1/7cpGO6yz9w+S+6V+DqYtRLm/r0wZc=; b=4c6f6+zRnws0MYaVy9s7KS0c7x3WLq98uaGdaBNGIbItBa+zB4PF78yWqPFS7xICrFxWev 7D53SUlNFDcXlnqA7FgiGeGF1un/FV+/xyHs1DeZ8MZnZDS7+GVhqpbwA5CKWgVR7e2ajN +MPk6f+TxNBENAs21z1z5eQwj5hldQM= X-Rspamd-Server: rspam04 X-Rspamd-Queue-Id: 364E81C0074 X-Stat-Signature: ry67zj331gwht4te3qauj11xa7b5f5r5 Authentication-Results: imf18.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=AkD5Kc6U; spf=none (imf18.hostedemail.com: domain of kirill.shutemov@linux.intel.com has no SPF policy when checking 134.134.136.126) smtp.mailfrom=kirill.shutemov@linux.intel.com; dmarc=pass (policy=none) header.from=intel.com X-Rspam-User: X-HE-Tag: 1655398453-457894 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 Thu, Jun 16, 2022 at 11:44:59AM +0200, Peter Zijlstra wrote: > > get_nr_threads() is the wrong thing. Either look at mm->mm_users or > > find a way to get rid of this restriction entirely. > > mm->mm_users should indeed be sufficient here. Hm. kthread_use_mm() doesn't bump mm_users. Do we care? -- Kirill A. Shutemov