From: "Gao, Liming" <liming.gao@intel.com>
To: "Zhu, Yonghong" <yonghong.zhu@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [Patch] BaseTools: not specified value of MAX_CONCURRENT_THREAD_NUMBER
Date: Tue, 6 Feb 2018 04:31:46 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E1C7CD5@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1517811271-8800-1-git-send-email-yonghong.zhu@intel.com>
Yonghong:
Please add the description for this behavior in target.template.
Thanks
Liming
>-----Original Message-----
>From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
>Yonghong Zhu
>Sent: Monday, February 05, 2018 2:15 PM
>To: edk2-devel@lists.01.org
>Subject: [edk2] [Patch] BaseTools: not specified value of
>MAX_CONCURRENT_THREAD_NUMBER
>
>when MAX_CONCURRENT_THREAD_NUMBER is not specified, tool will
>automatically detect number of processor threads.
>
>Fixes: https://bugzilla.tianocore.org/show_bug.cgi?id=775
>Contributed-under: TianoCore Contribution Agreement 1.1
>Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
>---
> BaseTools/Conf/target.template | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
>diff --git a/BaseTools/Conf/target.template
>b/BaseTools/Conf/target.template
>index 787fc64..d4b929d 100644
>--- a/BaseTools/Conf/target.template
>+++ b/BaseTools/Conf/target.template
>@@ -1,7 +1,7 @@
> #
>-# Copyright (c) 2006 - 2011, Intel Corporation. All rights reserved.<BR>
>+# Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.<BR>
> #
> # This program and the accompanying materials
> # are licensed and made available under the terms and conditions of the BSD
>License
> # which accompanies this distribution. The full text of the license may be
>found at
> # http://opensource.org/licenses/bsd-license.php
>@@ -57,14 +57,15 @@ TOOL_CHAIN_CONF = Conf/tools_def.txt
> # TAGNAME List Optional Specify the name(s) of the tools_def.txt
>TagName to use.
> # If not specified, all applicable TagName tools will be
> # used for the build. The list uses space character
>separation.
> TOOL_CHAIN_TAG = MYTOOLS
>
>-# MAX_CONCURRENT_THREAD_NUMBER NUMBER Optional The number
>of concurrent threads. Recommend to set this
>-# value to one more than the number of your
>compurter
>-# cores or CPUs. Less than 2 means disable
>multithread build.
>-MAX_CONCURRENT_THREAD_NUMBER = 1
>+# MAX_CONCURRENT_THREAD_NUMBER NUMBER Optional The number
>of concurrent threads. The default, if not
>+# specified or set to zero, tool automatically detect
>number
>+# of processor threads. Recommend to set this value
>to one
>+# more than the number of your compurter cores or
>CPUs.
>+# MAX_CONCURRENT_THREAD_NUMBER = 1
>
>
> # BUILD_RULE_CONF Filename Optional Specify the file name to use for the
>build rules that are followed
> # when generating Makefiles. If not specified, the file:
> # WORKSPACE/Conf/build_rule.txt will be used
>--
>2.6.1.windows.1
>
>_______________________________________________
>edk2-devel mailing list
>edk2-devel@lists.01.org
>https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2018-02-06 4:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 6:14 [Patch] BaseTools: not specified value of MAX_CONCURRENT_THREAD_NUMBER Yonghong Zhu
2018-02-06 4:31 ` Gao, Liming [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-08 1:50 Yonghong Zhu
2018-02-08 2:49 ` Gao, Liming
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A89E2EF3DFEDB4C8BFDE51014F606A14E1C7CD5@SHSMSX104.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox