Received: by 10.213.65.68 with SMTP id h4csp213534imn; Tue, 13 Mar 2018 01:37:16 -0700 (PDT) X-Google-Smtp-Source: AG47ELtXBykTNbq/dnlkRWEvotP+ilnY9WRblBCM6OWbg5KyYxTlB+ktgSn9JEuIWzEUyRPN6Y2u X-Received: by 10.98.57.215 with SMTP id u84mr10700292pfj.152.1520930236463; Tue, 13 Mar 2018 01:37:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1520930236; cv=none; d=google.com; s=arc-20160816; b=K7JAgH+RioWIEypx/eLjXk7ovBYRLTYPaS5Ue+md40YeISAzWLZUfL/vf5Nicet5+Y Ncr993hhRMWG2Honfb7RGTWHQCDWQLzWrG7kSajsSbNEYomvBmKSCSPz9JsFuPMEJmPl ZnWasLLM5QQZZXXwy3qpDPik+7WS6wUOlZpYIuHJnamjdS1HDQ+yuE6Ddek3AfzMhWtr gnAA1b2IVQTi5jj1/ac7zjPScmq5+5bnQNYlLydSHAu1f2j184B9kXsUC2dPOsagIyKa wfJlB9J8c9G1k24QS2AZLT48h8/Z1cQ4WHnbdfxNOIeZZaUzKi7lL0c/bpBVa4EIM0s+ /QOg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=FHCs9CxcKoqKo/w9YVsCrLn6zEwJ/G2xBBX+CdRG/bo=; b=fYkIivp9wUnTyJ790XVT/ghzHhZXGwwBPEkQ7xoo5IlPwVgC9ezweq0WjIDdccJ67b noOTpQ62mtNSp09kSr7TKoabeibUBDPOr81afAv/vXyJ8/MnITcfQaMchoWIuvmdJvNX MVu4QA9Mih9oYxBkO4TlKRFtX2D8/TA58Lk8+01kAlDr75d6qJoBM9574mKMFzgcU+Ly GuXGHz1UAeoIb1M5zLbw3YAQXFCX6Qcgc4aPjLbc67Ag6OUEIt8Su4KNeAntUs+8Rrrg nHl6EGcjRE8/ypNEbfsUK7IdYaySDc1gurKlpZSwnKvLQENS4FE+ePkSB5A8K3ffge3y owMQ== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t18si7269910pfg.246.2018.03.13.01.37.02; Tue, 13 Mar 2018 01:37:16 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752220AbeCMIgA (ORCPT + 99 others); Tue, 13 Mar 2018 04:36:00 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:51124 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751525AbeCMIf7 (ORCPT ); Tue, 13 Mar 2018 04:35:59 -0400 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 6969C7B4AD; Tue, 13 Mar 2018 08:35:58 +0000 (UTC) Received: from ming.t460p (ovpn-12-28.pek2.redhat.com [10.72.12.28]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 622B2111CB9C; Tue, 13 Mar 2018 08:35:44 +0000 (UTC) Date: Tue, 13 Mar 2018 16:35:41 +0800 From: Ming Lei To: Artem Bityutskiy Cc: Dou Liyang , Thomas Gleixner , Jens Axboe , Christoph Hellwig , linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, Laurence Oberman , "Rafael J. Wysocki" Subject: Re: [PATCH V3 0/4] genirq/affinity: irq vector spread among online CPUs as far as possible Message-ID: <20180313083535.GA21612@ming.t460p> References: <20180308105358.1506-1-ming.lei@redhat.com> <1520515113.20980.31.camel@gmail.com> <20180308133440.GA2713@ming.t460p> <20180309012458.GD5228@ming.t460p> <20180309120833.GB30257@ming.t460p> <5e5f3852-5314-c479-245e-d0a575e533a5@cn.fujitsu.com> <1520926721.20980.210.camel@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1520926721.20980.210.camel@gmail.com> User-Agent: Mutt/1.9.1 (2017-09-22) X-Scanned-By: MIMEDefang 2.78 on 10.11.54.3 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.1]); Tue, 13 Mar 2018 08:35:58 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.1]); Tue, 13 Mar 2018 08:35:58 +0000 (UTC) for IP:'10.11.54.3' DOMAIN:'int-mx03.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'ming.lei@redhat.com' RCPT:'' Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 13, 2018 at 09:38:41AM +0200, Artem Bityutskiy wrote: > On Tue, 2018-03-13 at 11:11 +0800, Dou Liyang wrote: > > I also > > met the situation that BIOS told to ACPI that it could support > > physical > > CPUs hotplug, But actually, there was no hardware slots in the > > machine. > > the ACPI tables like user inputs which should be validated when we > > use. > > This is exactly what happens on Skylake Xeon systems. When I check > dmesg or this file: > > /sys/devices/system/cpu/possible > > on 2S (two socket) and 4S (four socket) systems, I see the same number > 432. > > This number comes from ACPI MADT. I will speculate (did not see myself) > that 8S systems will report the same number as well, because of the > Skylake-SP (Scalable Platform) architecture. > > Number 432 is good for 8S systems, but it is way too large for 2S and > 4S systems - 4x or 2x larger than the theoretical maximum. > > I do not know why BIOSes have to report unrealistically high numbers, I > am just sharing my observation. > > So yes, Linux kernel's possible CPU count knowledge may be too large. > If we use that number to evenly spread IRQ vectors among the CPUs, we > end up with wasted vectors, and even bugs, as I observe on a 2S > Skylake. Then looks this issue need to fix by making possible CPU count accurate because there are other resources allocated according to num_possible_cpus(), such as percpu variables. Thanks, Ming