Received: by 10.213.65.68 with SMTP id h4csp3526406imn; Tue, 3 Apr 2018 06:34:09 -0700 (PDT) X-Google-Smtp-Source: AIpwx483QnwH6nVyq7GhVk12sxdWKkmq9sOazW54v9zECeawSHZj6J5FpbNHknjhoHkR6DxRjuWb X-Received: by 2002:a17:902:30f:: with SMTP id 15-v6mr13750085pld.365.1522762449397; Tue, 03 Apr 2018 06:34:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522762449; cv=none; d=google.com; s=arc-20160816; b=LlNLfdownyiNZDZb3TJucGOsNz4Swdr0orDE4F++uIGWtBOMKVnppfEeE479wCbsiB 9CEERFKNgcNAx00nt02bz2obKXtgl37yGaRnJ5DrVXRFqOGV4FU5CwDdaWgy8FqDaEQ4 tRqQWmNvfeGLxv2c0Z/m0DPWWjA+kc3mqs8eCyj/qcva52loeu76c1RCieA2ybTTTNps k40KyEXegio5UT8wfnAsjznfvt+0oQ2zcHgXhy94V9EpNu4s7GkljEsZjRWLTm0fMg3Z BJf/MJK/t9rot/Q+Q7FGZHKI5XPU4crK8NN082K7qNAkFMMZbRulYuxm9X2ZbDJoxwE9 sLUA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date :arc-authentication-results; bh=d0Ed2CxRORaWowTADmeVu3WQiQm7pKX0txfhl6Ty+24=; b=IJQy3jjJM7ldfJCSAdnOB3bNwK8L3Rrf/CFvGnAcBPIiQK1jcLD+ps1zXtWiI25g9k e+0sEzb0PPdpO7dv/pt7TfACrj6MvIzH+gCCf6Jk/j8tUwvhyToLPhE9BgGcx8wkcAEq g0NV2cOhDx5LCL86vMV/zl8lAF+cGt+DgH8Ruh/sbjXHEZghAqvcbd5FQbOLmStj0K0c g1nA52Nza3Vi+qFAUydsNl/6+eV5eNwVKQ9VHy7MXGbujnvCbJLxIPnh5ZHPzh8g4jG5 q/EdLcHTGi7yj+sr0HCYEa/NYMx7ZTaZ1H8QCcS8QrSSdxjIAIY1oJXzq4QtAn9f1+1I lmBg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g12-v6si544519plt.294.2018.04.03.06.33.54; Tue, 03 Apr 2018 06:34:09 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751217AbeDCNc1 (ORCPT + 99 others); Tue, 3 Apr 2018 09:32:27 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:59534 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750748AbeDCNc0 (ORCPT ); Tue, 3 Apr 2018 09:32:26 -0400 Received: from hsi-kbw-5-158-153-52.hsi19.kabel-badenwuerttemberg.de ([5.158.153.52] helo=nanos.tec.linutronix.de) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1f3M2v-0000OT-S0; Tue, 03 Apr 2018 15:32:22 +0200 Date: Tue, 3 Apr 2018 15:32:21 +0200 (CEST) From: Thomas Gleixner To: Ming Lei cc: Jens Axboe , Christoph Hellwig , linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, Laurence Oberman Subject: Re: [PATCH V3 4/4] genirq/affinity: irq vector spread among online CPUs as far as possible In-Reply-To: <20180308105358.1506-5-ming.lei@redhat.com> Message-ID: References: <20180308105358.1506-1-ming.lei@redhat.com> <20180308105358.1506-5-ming.lei@redhat.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 8 Mar 2018, Ming Lei wrote: > 1) before 84676c1f21 ("genirq/affinity: assign vectors to all possible CPUs") > irq 39, cpu list 0 > irq 40, cpu list 1 > irq 41, cpu list 2 > irq 42, cpu list 3 > > 2) after 84676c1f21 ("genirq/affinity: assign vectors to all possible CPUs") > irq 39, cpu list 0-2 > irq 40, cpu list 3-4,6 > irq 41, cpu list 5 > irq 42, cpu list 7 > > 3) after applying this patch against V4.15+: > irq 39, cpu list 0,4 > irq 40, cpu list 1,6 > irq 41, cpu list 2,5 > irq 42, cpu list 3,7 That's more or less window dressing. If the device is already in use when the offline CPUs get hot plugged, then the interrupts still stay on cpu 0-3 because the effective affinity of interrupts on X86 (and other architectures) is always a single CPU. So this only might move interrupts to the hotplugged CPUs when the device is initialized after CPU hotplug and the actual vector allocation moves an interrupt out to the higher numbered CPUs if they have less vectors allocated than the lower numbered ones. Probably not an issue for the majority of machines where ACPI stupidly claims that extra CPUs are possible while there is absolute no support for physical hotplug. Though in scenarios where "physical" hotplug is possible, e.g. virt, this might come surprising. Thanks, tglx