Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Victor Dumas <dumasv.dev@gmail.com>
Cc: Quentin Schulz <quentin.schulz@theobroma-systems.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4] support/scripts/fix-rpath: parallelize patching files
Date: Sun, 6 Aug 2023 23:33:55 +0200	[thread overview]
Message-ID: <20230806233355.4e92a27e@windsurf> (raw)
In-Reply-To: <20221020115030.483083-1-dumasv.dev@gmail.com>

On Thu, 20 Oct 2022 13:50:30 +0200
Victor Dumas <dumasv.dev@gmail.com> wrote:

> Using "xargs" instead of "while read" loop allows for the patching of files to be parallelized.
> This significantly reduces the amount of time it takes to fix all the paths.
> On a larger RFS(~300MB) this script was taking 5 minutes, it now only takes about 30s on a 12 core machine
> 
> Signed-off-by: Victor Dumas <dumasv.dev@gmail.com>
> ---
>  support/scripts/fix-rpath | 66 ++++++++++++++++++++++-----------------
>  1 file changed, 38 insertions(+), 28 deletions(-)

Applied to next after taking into account the feedback from Quentin
Schulz on using $(PARALLEL_JOBS) to specify the number of cores.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-08-06 21:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-03 12:24 [Buildroot] [PATCH] support/scripts/fix-rpath: parallelize patch files Victor Dumas
2022-10-06 13:18 ` Quentin Schulz via buildroot
2022-10-06 15:52   ` [Buildroot] [PATCH] support/scripts/fix-rpath: parallelize patching files Victor Dumas
2022-10-07  8:10     ` Quentin Schulz via buildroot
2022-10-07 15:50     ` [Buildroot] [PATCH v2] " Victor Dumas
2022-10-07 15:54     ` Victor Dumas
2022-10-19 12:40     ` [Buildroot] [PATCH v3] " Victor Dumas
2022-10-19 13:42       ` Angelo Compagnucci
2022-10-20 11:52       ` [Buildroot] [PATCH v4] " Victor Dumas
2022-10-20 11:55       ` Victor Dumas
2022-11-14 16:33         ` Quentin Schulz via buildroot
2022-11-15  8:47         ` David Laight
2022-11-15  9:24           ` Quentin Schulz via buildroot
2022-11-17 13:21             ` Gleb Mazovetskiy
2022-10-20 11:46     ` Victor Dumas
2022-10-20 11:50     ` Victor Dumas
2023-08-06 21:33       ` Thomas Petazzoni via buildroot [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=20230806233355.4e92a27e@windsurf \
    --to=buildroot@buildroot.org \
    --cc=dumasv.dev@gmail.com \
    --cc=quentin.schulz@theobroma-systems.com \
    --cc=thomas.petazzoni@bootlin.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