From: Peter Korsgaard <peter@korsgaard.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Herve Codina <herve.codina@bootlin.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] Revert "package/pkg-utils.mk: break hardlinks in global {TARGET, HOST}_DIR on per-package build"
Date: Thu, 26 Oct 2023 20:34:25 +0200 [thread overview]
Message-ID: <87il6tmdvy.fsf@48ers.dk> (raw)
In-Reply-To: <2b6e31b7385a7d104f7318010bdcdfbc1a2fbf25.1697576472.git.yann.morin.1998@free.fr> (Yann E. MORIN's message of "Tue, 17 Oct 2023 23:01:19 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> Commit 21d52e52d8de (package/pkg-utils.mk: break hardlinks in global
> {TARGET, HOST}_DIR on per-package build) stopped hardlink the source and
> destination when rsyncing per-package directory, on the rationale that
> modifying files in-place after the rsync would also modify the original
> file, and that break foo-rebuild and can cause issues with post-build
> scripts.
> However, what 21d52e52d8de did not envision, is that copying instead of
> hard-linking has two nasty side effects:
> - the size increase for the build directory increase with the number
> of packages and with the depth of th dependency chains for those
> packages: a (relatively small) build that was previously totalling
> ~13GiB in output/, now totals north of 122GiB, an almost 10-time
> increase;
> - the build time increases, as it takes mopre time to read+write files
> than it takes to create a new link to a file; the same build saw a
> increase of build time from 5min 10s to 7min 30s, a 45% increase.
> These regressions are both serious, so revert the change; we'll come up
> with a stopgap measure in follow-up commits.
> This reverts commit 21d52e52d8dee0940d28b3a38551eb183be37813.
> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
> Cc: Herve Codina <herve.codina@bootlin.com>
> Cc: Peter Korsgaard <peter@korsgaard.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Committed to 2023.02.x and 2023.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-10-26 18:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 21:01 [Buildroot] [PATCH 0/2] package/pkg-utils: fix regression in size and build time with PPD (branch yem/rsync-copy) Yann E. MORIN
2023-10-17 21:01 ` [Buildroot] [PATCH 1/2] Revert "package/pkg-utils.mk: break hardlinks in global {TARGET, HOST}_DIR on per-package build" Yann E. MORIN
2023-10-18 8:38 ` Herve Codina via buildroot
2023-10-26 18:34 ` Peter Korsgaard [this message]
2023-10-17 21:01 ` [Buildroot] [PATCH 2/2] package/pkg-utils: teach per-package-rsync to copy or hardlink dest Yann E. MORIN
2023-10-18 8:53 ` Herve Codina via buildroot
2023-10-18 15:20 ` Yann E. MORIN
2023-10-18 15:38 ` Herve Codina via buildroot
2023-10-18 16:18 ` Yann E. MORIN
2023-10-18 16:42 ` Herve Codina via buildroot
2023-10-26 18:34 ` Peter Korsgaard
2023-10-21 19:25 ` [Buildroot] [PATCH 0/2] package/pkg-utils: fix regression in size and build time with PPD (branch yem/rsync-copy) Yann E. MORIN
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=87il6tmdvy.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=herve.codina@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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