Received: by 10.213.65.68 with SMTP id h4csp1103269imn; Wed, 21 Mar 2018 02:43:44 -0700 (PDT) X-Google-Smtp-Source: AG47ELsK2RSrVDt2Fu1wBxv7a94OxN1BjPvLQ6vQC96GlMw2hVpbzWloAK3SLa2GzxiH/R+bpo0e X-Received: by 10.99.180.6 with SMTP id s6mr9215466pgf.81.1521625424710; Wed, 21 Mar 2018 02:43:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521625424; cv=none; d=google.com; s=arc-20160816; b=G4k1IvwclrPUJ318Rq5MwPPauvaXz346JPxOVvQUUSI7dPQolouTkhH5gyMM3SCXZG XEj+u9X9UAUMMFoiYunDZ+XS3fDB5kixMRvR6ZxiSY7APpiwfVb6fcD68zAeMew3wHmY HwXlUSBfm4QZHGoOFPx8WEE1VcfMWq+moTQ31Qy+njTQBFnDSImL1/dysnsPiAiLqYTu NxnwTY/szv1TigL+q+jBAJiMEGvr4qXEdEjI+KWSBf3yRVAWosI+mbUNTRFzUhCS9kRC INQT1Ya1vWV9BUaDwVtl3B0kT4OWnhkTHquSWhPexTBGnPwwP2WCRCvOLwNKaEVAhWIT 9TjA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=rI2CoDlNQStzi0sFVCxi7lHOP+5IAcapNVIa1uNUkl0=; b=HE9XQar1E1xLCAAc7eG5MHO5BW2q3SkIPcIBnbLn9IA4oxeONVpVq3WmUTEsABLGGe VtKCs2HJXxQKVHdj6Yheo8CGhZtSKfPzAO8KFzLtFjIZLXb/Yl+t3tSJSxRsmDtyxuY3 TkxPAN90gecqRVVnhhAWK9bK5tQ3bidK2zT+DBWEKE8PFj0Do4PamjVM1/8q7ggsHkF4 fglTuMvRWH2NAl7QxanK+ArdfUMtZLxePJao/wf785lc/8jOokQ5QeipEnPGlkUkuYkw WlyZaDebfSaHDbSFgVCyAw8wSSvhp1zCHKJyAfZof1KyYjJdBN8PAqApUZNwL3XVSthC b3fA== 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 g1-v6si3458891plt.54.2018.03.21.02.43.30; Wed, 21 Mar 2018 02:43:44 -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 S1751888AbeCUJl4 (ORCPT + 99 others); Wed, 21 Mar 2018 05:41:56 -0400 Received: from mail.cn.fujitsu.com ([183.91.158.132]:19123 "EHLO heian.cn.fujitsu.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751728AbeCUJlx (ORCPT ); Wed, 21 Mar 2018 05:41:53 -0400 X-IronPort-AV: E=Sophos;i="5.43,368,1503331200"; d="scan'208";a="38036313" Received: from unknown (HELO cn.fujitsu.com) ([10.167.33.5]) by heian.cn.fujitsu.com with ESMTP; 21 Mar 2018 17:41:52 +0800 Received: from G08CNEXCHPEKD02.g08.fujitsu.local (unknown [10.167.33.83]) by cn.fujitsu.com (Postfix) with ESMTP id 5D67F4D0EFC9; Wed, 21 Mar 2018 17:41:48 +0800 (CST) Received: from localhost.localdomain (10.167.226.106) by G08CNEXCHPEKD02.g08.fujitsu.local (10.167.33.89) with Microsoft SMTP Server (TLS) id 14.3.361.1; Wed, 21 Mar 2018 17:41:47 +0800 Subject: Re: [PATCH 1/5] x86/smpboot: Add the missing description of possible_cpus To: Peter Zijlstra CC: , , , , , , , , , References: <20180320110432.28127-1-douly.fnst@cn.fujitsu.com> <20180320110432.28127-2-douly.fnst@cn.fujitsu.com> <20180320123712.GR4043@hirez.programming.kicks-ass.net> <20180321090826.GW4043@hirez.programming.kicks-ass.net> <076196e1-c181-ba44-f912-61bd279b345b@cn.fujitsu.com> From: Dou Liyang Message-ID: <1dfcdb3d-6a92-8654-7cc4-ef262ddb0915@cn.fujitsu.com> Date: Wed, 21 Mar 2018 17:41:45 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <076196e1-c181-ba44-f912-61bd279b345b@cn.fujitsu.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Originating-IP: [10.167.226.106] X-yoursite-MailScanner-ID: 5D67F4D0EFC9.AE15B X-yoursite-MailScanner: Found to be clean X-yoursite-MailScanner-From: douly.fnst@cn.fujitsu.com X-Spam-Status: No Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org At 03/21/2018 05:34 PM, Dou Liyang wrote: > Hi Peter, > > At 03/21/2018 05:08 PM, Peter Zijlstra wrote: >> On Wed, Mar 21, 2018 at 01:33:24PM +0800, Dou Liyang wrote: >>> How about: >>> >>> possible_cpus=    [s390,x86_64] Set the number of possible CPUs which >>>         are determined by the ACPI tables MADT or mptables by >>>         default. possible_cpus=n : n >= 1 enforces the possible >>>         number to be 'n'. >>>         While nr_cpus is also be set: nr_cpus=m, choice the >>>         minimum one for the number of possible CPUs. >> >> So what is the exact difference between possible_cpus and nr_cpus ? I > > the possible_cpus= can reset the number of possible CPUs, even bigger > than 'num_processors + disabled_cpus', But nr_cpus= can't. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the maximum number kernel gets from ACPI/mptables, no matter what number nr_cpus= is, the number of possible CPUs will not bigger than it. > >> konw maxcpus= limits the number of CPUs we bring up, and possible_cpus >> limits the possible_map, but I'm not entirely sure what nr_cpus does >> here. >> > > nr_cpus can limited the maximum CPUs that the kernel could support. > > Here is a double check in case of using them at the same time, even if I > think just using possible_cpus= is enough. :-) > > Thanks, >     dou. >> >>