Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp6012375rwl; Tue, 4 Apr 2023 06:48:57 -0700 (PDT) X-Google-Smtp-Source: AKy350YBRbWr0ULb7Jwu/ahwwldrKZuWaOfErTXiXtVWQuWDz+zqBjuVEGgKWdXLTitn7InxE+pi X-Received: by 2002:a05:6402:1a46:b0:4fa:3b3:c867 with SMTP id bf6-20020a0564021a4600b004fa03b3c867mr2624432edb.17.1680616137457; Tue, 04 Apr 2023 06:48:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1680616137; cv=none; d=google.com; s=arc-20160816; b=kznYc+vUnzmSY+maf125esLcxYXRpj9M0Nv46o3PfmfCcJhcGO21PZUtwu1qtSWY/R NYyS/4SYIIbSJ87oJvfSqvLmAhFCzTZ1k3GMOSTfPX6Wd79XDWqbN2DDDipITq1XMkBM CU3j/BkFrko+dtB911jOwTxROewMt5V88+YS1qqfI0fHGteqn8IIqHH0zvkjaqaDdBxc rk2adbDpgJlfEqwmd5UjwyYfGvsXg8JyRFjXxgXbMzLkMRtesXCo5Kh1VEFbSIKCboRx 6Uv/S49sybN1kSKcWmheNucEziU24xwESagXeAcOq5tHdTk4kTyjpmQH1+au4EN3HNdc m8iA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=eOn+GooQef0PZGSR4LECkucKGIH5iRWxz3Wp3EiY8Go=; b=ExZIoMXfJl2aAp5GpyhdKZ/IVA+qBccV9Nb50AFjat267/l4ozo0AKQ4j7SOYSVF6w LCQUWZIi1eoj5eKMfqX1dN6++0W3ClzVcIGIWIrL4ZMM+1vwmd0eUI41Jy5Y6Q7idubw s9oa1E3g8t6r+h0ieacYCLG9to6Eq8BvVo+Vh7iGlZLYiRpsSIGgbpPDy1h0kbwg410v s2wkH5SKIImPdrXd3qS99FVh1Aku4Kr28z1DI59csDTr39AGHR8JrN5jZvMLmdR2cW7i ffNKJfEdY13ldGmfJG9clFZKPW2W0HcSkIszGABs3ah/4cJTONYFNW86CNJueHwD8vCq wZqw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Q4A1PZMH; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id c9-20020a056402120900b004acda72375fsi10469733edw.84.2023.04.04.06.48.32; Tue, 04 Apr 2023 06:48:57 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Q4A1PZMH; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235204AbjDDNns (ORCPT + 99 others); Tue, 4 Apr 2023 09:43:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33310 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234453AbjDDNnq (ORCPT ); Tue, 4 Apr 2023 09:43:46 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ADBF03C0F for ; Tue, 4 Apr 2023 06:42:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1680615775; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=eOn+GooQef0PZGSR4LECkucKGIH5iRWxz3Wp3EiY8Go=; b=Q4A1PZMH/3oWU8Y0Vqw0Y+aFINdfkLgQH1AbhBRs8BO71OVwa2nScDgG6Ea6MHSzerMwWd 92qTPq/kCT5YW2NUP3ec4+DAUkycxageMHg32hGpr+ELYJBYXMRVPgpf9YIxxYbTliNJ7v CvvPy1ox6VpqUTXVx3uFeW6fb+fK1sw= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-648-5BjHu8A0ORC4zh0ZPovsnQ-1; Tue, 04 Apr 2023 09:42:50 -0400 X-MC-Unique: 5BjHu8A0ORC4zh0ZPovsnQ-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id E0B332A59564; Tue, 4 Apr 2023 13:42:48 +0000 (UTC) Received: from ypodemsk.tlv.csb (unknown [10.39.194.160]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 41AAB2166B29; Tue, 4 Apr 2023 13:42:40 +0000 (UTC) From: Yair Podemsky To: linux@armlinux.org.uk, mpe@ellerman.id.au, npiggin@gmail.com, christophe.leroy@csgroup.eu, hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com, borntraeger@linux.ibm.com, svens@linux.ibm.com, davem@davemloft.net, tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com, will@kernel.org, aneesh.kumar@linux.ibm.com, akpm@linux-foundation.org, peterz@infradead.org, arnd@arndb.de, keescook@chromium.org, paulmck@kernel.org, jpoimboe@kernel.org, samitolvanen@google.com, frederic@kernel.org, ardb@kernel.org, juerg.haefliger@canonical.com, rmk+kernel@armlinux.org.uk, geert+renesas@glider.be, tony@atomide.com, linus.walleij@linaro.org, sebastian.reichel@collabora.com, nick.hawkins@hpe.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org, sparclinux@vger.kernel.org, linux-arch@vger.kernel.org, linux-mm@kvack.org, mtosatti@redhat.com, vschneid@redhat.com, dhildenb@redhat.com Cc: ypodemsk@redhat.com, alougovs@redhat.com Subject: [PATCH 0/3] send tlb_remove_table_smp_sync IPI only to necessary CPUs Date: Tue, 4 Apr 2023 16:42:21 +0300 Message-Id: <20230404134224.137038-1-ypodemsk@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 3.1 on 10.11.54.6 X-Spam-Status: No, score=-0.2 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Currently the tlb_remove_table_smp_sync IPI is sent to all CPUs indiscriminately, this causes unnecessary work and delays notable in real-time use-cases and isolated cpus. By limiting the IPI to only be sent to cpus referencing the effected mm and in kernel mode latency is improved. a config to differentiate architectures that support mm_cpumask from those that don't will allow safe usage of this feature. Yair Podemsky (3): arch: Introduce ARCH_HAS_CPUMASK_BITS mm/mmu_gather: send tlb_remove_table_smp_sync IPI only to MM CPUs mm/mmu_gather: send tlb_remove_table_smp_sync IPI only to CPUs in kernel mode -- 2.31.1