From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH 0/3] get_abi: improve message output and fix a regression
Date: Tue, 28 Sep 2021 19:19:22 +0200 [thread overview]
Message-ID: <YVNOmoM7DZfJ2BoJ@kroah.com> (raw)
In-Reply-To: <20210928154353.2e6656bb@coco.lan>
On Tue, Sep 28, 2021 at 03:43:53PM +0200, Mauro Carvalho Chehab wrote:
> Em Tue, 28 Sep 2021 14:27:39 +0200
> Mauro Carvalho Chehab <mchehab+huawei@kernel.org> escreveu:
>
> > Em Tue, 28 Sep 2021 13:04:22 +0200
> > Greg Kroah-Hartman <gregkh@linuxfoundation.org> escreveu:
> >
> > > On Tue, Sep 28, 2021 at 12:14:01PM +0200, Mauro Carvalho Chehab wrote:
> > > > Hi Greg,
> > > >
> > > > As promised on
> > > >
> > > > https://lore.kernel.org/lkml/20210928120304.62319fba@coco.lan/T/#u
> > > >
> > > > I'm adding progress info when get_abi.pl is checking for undefined ABI symbols
> > > > on patches 1 and 2.
> > > >
> > > > That will help not only to identify what is causing delays on the script, but also
> > > > to notify the user that processing it could take some time on some systems.
> > > >
> > > > If you run it on your big server with:
> > > >
> > > > scripts/get_abi.pl undefined 2>logs
> > > >
> > > > The "logs" file will contain timestamps relative to the time the script started to
> > > > do the regex matches for sysfs files. It should be printing one line every
> > > > time the progress completes 1% or one second after the last progress output.
> > >
> > > Adding more debugging and tweaking the script a bit to show the file it
> > > is about to check, not the one it finished checking,
> >
> > Feel free to modify the script and add such debug/tweaks if you find
> > it useful.
> >
> > > I got the following
> > > debug output that seems to pinpoint the problem file.
> > >
> > > The sysfs file that is causing problems is:
> > > /sys/devices/pci0000:40/0000:40:00.2/iommu/ivhd1/amd-iommu/cap
> > >
> >
> > Btw, I just got an arm64 server with 128 CPUs for testing. I'm trying
> > to allocate also a big x86 server here, but I'm not sure if it is AMD or
> > Intel.
>
> Some tests on a Gigabyte R182-Z91-00 server, equipped with AMD EPYC 7352
> 24-Core Processors (total 96 threads):
>
> $ find /sys |wc -l
> 233981
>
> $ time ./scripts/get_abi.pl undefined >undefined 2>logs
>
> real 0m38.917s
> user 0m34.554s
> sys 0m4.292s
>
> PS.: this machine doesn't have anything at /sys/class/iommu.
>
> On a Huawei TaiShan 200 (Model 2280) with 128 ARM cores:
>
> $ find /sys |wc -l
> 99362
> $ time ./scripts/get_abi.pl undefined >undefined 2>logs
>
> real 0m29.311s
> user 0m26.173s
> sys 0m3.061s
>
> Both machines are using Perl 5.26.
Try it with your sorting patch, that fixed it for me and now it runs in
10 seconds.
crazy.
next prev parent reply other threads:[~2021-09-28 17:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 10:14 [PATCH 0/3] get_abi: improve message output and fix a regression Mauro Carvalho Chehab
2021-09-28 10:14 ` [PATCH 1/3] scripts: get_abi.pl: use STDERR for search-string and show-hints Mauro Carvalho Chehab
2021-09-28 10:14 ` [PATCH 2/3] scripts: get_abi.pl: show progress Mauro Carvalho Chehab
2021-09-28 10:14 ` [PATCH 3/3] ABI: evm: place a second what at the next line Mauro Carvalho Chehab
2021-09-28 11:04 ` [PATCH 0/3] get_abi: improve message output and fix a regression Greg Kroah-Hartman
2021-09-28 12:27 ` Mauro Carvalho Chehab
2021-09-28 13:43 ` Mauro Carvalho Chehab
2021-09-28 17:19 ` Greg Kroah-Hartman [this message]
2021-09-28 17:18 ` Greg Kroah-Hartman
2021-09-28 21:51 ` [PATCH] scripts: get_abi.pl: make undefined search more deterministic Mauro Carvalho Chehab
2021-09-29 7:13 ` Greg Kroah-Hartman
2021-09-28 21:54 ` [PATCH 0/3] get_abi: improve message output and fix a regression Mauro Carvalho Chehab
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=YVNOmoM7DZfJ2BoJ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.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 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 NNTP newsgroup(s).