public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Henning Schild" <henning.schild@siemens.com>,
	isar-users@googlegroups.com
Subject: Re: [PATCH] bitbake.conf: set BB_NICE_LEVEL to lower task prios
Date: Thu, 22 Aug 2019 13:03:15 +0200	[thread overview]
Message-ID: <c811e64f-16e3-d7a7-dd54-8e58e1367b70@siemens.com> (raw)
In-Reply-To: <20190822091546.21698-1-henning.schild@siemens.com>

On 22.08.19 11:15, [ext] Henning Schild wrote:
> From: Henning Schild <henning.schild@siemens.com>
> 
> Setting this makes your machine more "usable" while waiting for those
> Isar builds.
> 
> Signed-off-by: Henning Schild <henning.schild@siemens.com>
> ---
>   meta/conf/bitbake.conf | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 3d18223..6625b33 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -89,6 +89,7 @@ BB_SIGNATURE_HANDLER ?= "basichash"
>   BB_STAMP_POLICY ?= "full"
>   
>   BB_NUMBER_THREADS ?= "${@bb.utils.cpu_count()}"
> +BB_NICE_LEVEL ?= "10"
>   
>   BBINCLUDELOGS ??= "yes"
>   
> 

Not set by OE by default. Isn't that something for local tuning?

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2019-08-22 11:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-22  9:15 Henning Schild
2019-08-22 11:03 ` Jan Kiszka [this message]
2019-08-22 11:15   ` Henning Schild
2019-08-22 11:24     ` Baurzhan Ismagulov
2019-08-22 12:03       ` Henning Schild
2019-08-22 12:12         ` Jan Kiszka

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-all 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=c811e64f-16e3-d7a7-dd54-8e58e1367b70@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    /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