From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 8CD718217E for ; Thu, 23 Feb 2017 15:11:10 -0800 (PST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga105.jf.intel.com with ESMTP; 23 Feb 2017 15:11:10 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.35,198,1484035200"; d="scan'208";a="52042886" Received: from orsmsx108.amr.corp.intel.com ([10.22.240.6]) by orsmga002.jf.intel.com with ESMTP; 23 Feb 2017 15:11:10 -0800 Received: from orsmsx152.amr.corp.intel.com (10.22.226.39) by ORSMSX108.amr.corp.intel.com (10.22.240.6) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 23 Feb 2017 15:11:10 -0800 Received: from orsmsx114.amr.corp.intel.com ([169.254.8.253]) by ORSMSX152.amr.corp.intel.com ([169.254.8.156]) with mapi id 14.03.0248.002; Thu, 23 Feb 2017 15:11:09 -0800 From: "Richardson, Brian" To: Rebecca Cran , "Brian J. Johnson" , "Wei, David" , "Gao, Liming" , "edk2-devel@lists.01.org" CC: "Lu, ShifeiX A" , "Zimmer, Vincent" , Andrew Fish Thread-Topic: [edk2] Improvements to build system etc. for edk2-platforms devel-MinnowBoard3? Thread-Index: AQHSjKnkFqzr0YqW2kOL3svWeEuMU6F0+0aAgAAQCoCAACzV8IAAjMyA//+c6tCAAZEPAIAAir2A//+7pwA= Date: Thu, 23 Feb 2017 23:11:09 +0000 Message-ID: <80AC2BAA3152784F98F581129E5CF5AF665616CD@ORSMSX114.amr.corp.intel.com> References: <4A89E2EF3DFEDB4C8BFDE51014F606A14D6E27B3@shsmsx102.ccr.corp.intel.com> <95a8d930-6bb2-e666-1957-8d78a25efd10@bluestop.org> <80AC2BAA3152784F98F581129E5CF5AF6655EC20@ORSMSX114.amr.corp.intel.com> <2d7462e9-de6c-67b2-ffd7-a3fa194ce06b@bluestop.org> <80AC2BAA3152784F98F581129E5CF5AF6655F06F@ORSMSX114.amr.corp.intel.com> <89954A0B46707A448411A627AD4EEE3468EFDFFF@SHSMSX101.ccr.corp.intel.com> In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYzU4OWNlY2QtMDg3Mi00Zjk5LTgyZTEtMjI5NjQ4ZTQ3YzAxIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6ImQxUGYzSzhXdVNtSm9tSzNPeHQxUStZdE1DME5mODQ0c1dXcTZteWRKVW89In0= x-originating-ip: [10.22.254.139] MIME-Version: 1.0 Subject: Re: Improvements to build system etc. for edk2-platforms devel-MinnowBoard3? X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2017 23:11:10 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable One thing we can try is automating the right setting for MAX_CONCURRENT_THR= EAD_NUMBER. In Windows, there's a command line utility to return the number= of logical processors. C:\Users\sample>wmic cpu get numberoflogicalprocessors NumberOfLogicalProcessors 4=20 This could be used to set MAX_CONCURRENT_THREAD_NUMBER (NumberOfLogicalProc= essors+1, so 5 in this case) automagically in target.txt (via edksetup.bat)= or as a command line parameter (in BuildBios.bat). I'm sure there's an equ= ivalent shell command in Linux that can be co-opted for our purposes. Thoughts? Thanks ... br --- Brian Richardson, Senior Technical Marketing Engineer, Intel Software brian.richardson@intel.com -- @intel_Brian (Twitter & WeChat) https://software.intel.com/en-us/meet-the-developers/evangelists/team/brian= -richardson=20 -----Original Message----- From: Rebecca Cran [mailto:rebecca@bluestop.org]=20 Sent: Thursday, February 23, 2017 2:10 PM To: Brian J. Johnson ; Wei, David ; Richardson, Brian ; Gao, Liming ; edk2-devel@lists.01.org Cc: Lu, ShifeiX A ; Zimmer, Vincent ; Andrew Fish Subject: Re: [edk2] Improvements to build system etc. for edk2-platforms de= vel-MinnowBoard3? On 2/23/2017 11:53 AM, Brian J. Johnson wrote: > Sorry if I'm bikeshedding... NUMBER_OF_PROCESSORS isn't a good=20 > default for those of us who build on servers with hundreds of threads=20 > available. The OS, disks, and build.exe/build.py become bottlenecks. > Maybe we could put a cap (say, 20) on the default thread limit, so it=20 > uses NUMBER_OF_PROCESSORS or 20 threads, whichever is less. > > Or just set a small, fixed number of threads by default and document=20 > better how to change it, as others suggested. Good point. I think the best approach will be to have a --setup parameter w= hich configures defaults in Conf/target.txt, after which users can change M= AX_CONCURRENT_THREAD_NUMBER - instead of the current method which involves = figuring out which of files ends up running build.exe with '-n '. --=20 Rebecca