From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mike Looijmans <mike.looijmans@topic.nl>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/2] bitbake.conf: Ensure XZ_THREADS doesn't change sstate checksums
Date: Thu, 30 Sep 2021 10:47:52 +0100 [thread overview]
Message-ID: <38f7a46fd43f411aedcf622891cab8985f9f9130.camel@linuxfoundation.org> (raw)
In-Reply-To: <9b55887d-d2ce-5443-5e4d-be7f4133d5f7@topic.nl>
On Thu, 2021-09-30 at 08:50 +0200, Mike Looijmans wrote:
> Wouldn't "0" be a better default? Setting threads to "0" will make xz use the
> CPU count anyway, so it'd be honest too.
On some systems we have this set to a specific value rather than auto so any
value is potentially dishonest. I think I went for "1" as it was clearly the
least likely and more obvious when looking at the sig files to see if it was
working.
At the end of the day it doesn't really matter as long as it is a specific
value.
Cheers,
Richard
prev parent reply other threads:[~2021-09-30 9:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-11 10:04 [PATCH 1/2] bitbake.conf: Ensure XZ_THREADS doesn't change sstate checksums Richard Purdie
2021-09-11 10:04 ` [PATCH 2/2] sstate: Avoid problems with recipes using SRCPV when fetching sstate Richard Purdie
[not found] ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.d232f846-51ae-43c0-85e8-be1b07245956@emailsignatures365.codetwo.com>
[not found] ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.0d2bd5fa-15cc-4b27-b94e-83614f9e5b38.5a416b0f-56e3-45c8-b87b-0760607e2824@emailsignatures365.codetwo.com>
2021-09-30 6:50 ` [OE-core] [PATCH 1/2] bitbake.conf: Ensure XZ_THREADS doesn't change sstate checksums Mike Looijmans
2021-09-30 8:38 ` Jose Quaresma
2021-09-30 9:47 ` Richard Purdie [this message]
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=38f7a46fd43f411aedcf622891cab8985f9f9130.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=mike.looijmans@topic.nl \
--cc=openembedded-core@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.