From d05a268c5069c3fb47ceed47862ba36b5f49ebd3 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 18 Jun 2018 15:06:16 -0700 Subject: bitbake: bitbake-user-manual: Added "number_threads" varflag You can now limit on a task-specific basis the number of threads a task will use. This is useful for machines that have high numbers of cores and need to be rate-limited due to various resource constraints. (Bitbake rev: 4937ed392fdc4442dd91f644f329dda29f27242c) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../bitbake-user-manual-metadata.xml | 32 ++++++++++++++++++++++ 1 file changed, 32 insertions(+) (limited to 'bitbake/doc') diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml index b4fc64e753..bc08c814d1 100644 --- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml +++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml @@ -1929,6 +1929,38 @@ not careful. + [number_threads]: + Limits tasks to a specific number of simultaneous threads + during execution. + This varflag is useful when your build host has a large number + of cores but certain tasks need to be rate-limited due to various + kinds of resource constraints (e.g. to avoid network throttling). + number_threads works similarly to the + BB_NUMBER_THREADS + variable but is task-specific. + + Set the value globally. + For example, the following makes sure the + do_fetch task uses no more than two + simultaneous execution threads: + + do_fetch[number_threads] = "2" + + Warnings + + + Setting the varflag in individual recipes rather + than globally can result in unpredictable behavior. + + + Setting the varflag to a value greater than the + value used in the BB_NUMBER_THREADS + variable causes number_threads + to have no effect. + + + + [postfuncs]: List of functions to call after the completion of the task. -- cgit v1.2.3-54-g00ecf