From: Panu Matilainen <pmatilai@redhat.com>
To: Kalev Lember <klember@redhat.com>
Cc: debugedit@sourceware.org
Subject: Re: [PATCH] find-debuginfo: Pass -j down to dwz
Date: Fri, 20 Jan 2023 13:27:39 +0200 [thread overview]
Message-ID: <b4e0162f-dfbd-968f-8d35-14b18bacf8b4@redhat.com> (raw)
In-Reply-To: <CAHjaNbrcJUy1HZ1sp+CUzqAk2nuY9P5g+_gMd_dhvGm4-KG2+w@mail.gmail.com>
On 1/20/23 12:27, Kalev Lember wrote:
> On Fri, Jan 20, 2023 at 9:40 AM Panu Matilainen <pmatilai@redhat.com
> <mailto:pmatilai@redhat.com>> wrote:
>
> On 1/19/23 18:03, Kalev Lember wrote:
> > Now that dwz 0.15 supports parallel jobs, add a way to control it
> from
> > here. find-debuginfo already has a -j parameter so we can just
> extend it
> > and pass the value down to dwz as well.
> >
> > This should fix building large packages on memory constrained
> builders,
> > such as webkitgtk on s390x in Fedora koji build system, where we
> can now
> > use the -j option to tune down parallelism to avoid running out of
> > memory during dwz run.
> >
> > Signed-off-by: Kalev Lember <klember@redhat.com
> <mailto:klember@redhat.com>>
> > ---
> > scripts/find-debuginfo.in <http://find-debuginfo.in> | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/scripts/find-debuginfo.in <http://find-debuginfo.in>
> b/scripts/find-debuginfo.in <http://find-debuginfo.in>
> > index b07a52f..8cc1bfd 100755
> > --- a/scripts/find-debuginfo.in <http://find-debuginfo.in>
> > +++ b/scripts/find-debuginfo.in <http://find-debuginfo.in>
> > @@ -585,7 +585,7 @@ if $run_dwz \
> > dwz_multifile_suffix=".${dwz_multifile_idx}"
> > done
> >
> dwz_multifile_name="${dwz_multifile_name}${dwz_multifile_suffix}"
> > - dwz_opts="-h -q -r"
> > + dwz_opts="-h -q -r -j ${n_jobs}"
> > [ ${#dwz_files[@]} -gt 1 ] && [ "$dwz_single_file_mode" =
> "false" ] \
> > && dwz_opts="${dwz_opts} -m .dwz/${dwz_multifile_name}"
> > mkdir -p "${RPM_BUILD_ROOT}/usr/lib/debug/.dwz"
>
> This is so new, even Fedora 37 doesn't have it yet. I tend to think
> find-debuginfo should be a bit conservative about the assumptions it
> makes about external tools.
>
>
> Can we do some kind of configure check then and require the latest dwz?
> Or add this as a downstream patch in rawhide?
>
> The problem is that new dwz is already in rawhide and it broke webkitgtk
> builds due to too much memory use. The ppc64le and s390x builders just
> don't have enough memory now to do dwz on webkitgtk. Passing down the -j
> option would help us control the memory use to get the builds going again.
>
Oh, if rawhide needs this then rawhide needs this, I don't mind that at
all. I just think that upstream find-debuginfo shouldn't assume "latest
everything" any more than rpm can do so.
configure-time check seems reasonable to me.
- Panu -
next prev parent reply other threads:[~2023-01-20 11:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 16:03 Kalev Lember
2023-01-20 8:39 ` Panu Matilainen
2023-01-20 10:27 ` Kalev Lember
2023-01-20 11:27 ` Panu Matilainen [this message]
2023-01-26 14:34 ` Mark Wielaard
2023-01-26 15:57 ` Kalev Lember
2023-01-26 23:14 ` Mark Wielaard
2023-01-27 17:37 ` Mark Wielaard
2023-01-28 1:07 ` Kalev Lember
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=b4e0162f-dfbd-968f-8d35-14b18bacf8b4@redhat.com \
--to=pmatilai@redhat.com \
--cc=debugedit@sourceware.org \
--cc=klember@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).