From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Quentin Schulz <quentin.schulz@theobroma-systems.com>,
Wes Lindauer <wesley.lindauer@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH] bitbake.conf: Add resource vars to hash ignore list
Date: Mon, 22 Aug 2022 12:18:58 +0100 [thread overview]
Message-ID: <01dce5b603bc47fc195ba4ea738e7a333ac1992e.camel@linuxfoundation.org> (raw)
In-Reply-To: <cf290a54-3b62-9c0d-32cc-08195f682b99@theobroma-systems.com>
On Mon, 2022-08-22 at 11:28 +0200, Quentin Schulz wrote:
> Hi Wes,
>
> On 8/22/22 06:59, Wes Lindauer wrote:
> > It should not matter what xz/zstd parallelism and resource usage is set to
> > when determining hash signatures. This allows sharing more sstate across
> > host machines with different CPU configurations.
> >
>
> It seems like it does matter in some ways, c.f.:
> https://git.openembedded.org/openembedded-core/commit/?id=0296dc71c01d1b7953d74ef37d56429e2f4fcfab
> and
> https://git.openembedded.org/openembedded-core/commit/?id=e72c0b94554a9bc293844ec2bddb0c04ea19791d
As Quentin mentions, the value does matter. In particular, those
compiled with a single thread differ to those with multiple threads. As
such the proposed patch can't be accepted.
Cheers,
Richard
next prev parent reply other threads:[~2022-08-22 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 4:59 [OE-core][PATCH] bitbake.conf: Add resource vars to hash ignore list Wes Lindauer
2022-08-22 7:16 ` Ernst Sjöstrand
2022-08-22 9:28 ` Quentin Schulz
2022-08-22 11:18 ` Richard Purdie [this message]
2022-08-22 13:17 ` Peter Kjellerstedt
2022-08-30 19:27 ` Wes Lindauer
2022-08-30 19:41 ` Richard Purdie
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=01dce5b603bc47fc195ba4ea738e7a333ac1992e.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=quentin.schulz@theobroma-systems.com \
--cc=wesley.lindauer@gmail.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 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.