From: Alexey Dobriyan <adobriyan@gmail.com>
To: mmarek@suse.cz, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] tags: much faster, parallel "make tags"
Date: Tue, 14 Apr 2015 20:20:47 +0300 [thread overview]
Message-ID: <20150414172047.GA5641@p183.telecom.by> (raw)
ctags is single-threaded program. Split list of files to be tagged into
equal parts, 1 part for each CPU and then merge the results.
Speedup on one 2-way box I have is ~143 s => ~99 s (-31%).
On another 4-way box: ~120 s => ~65 s (-46%!).
Resulting "tags" files aren't byte-for-byte identical because ctags
program numbers anon struct and enum declarations with "__anonNNN"
symbols. If those lines are removed, "tags" file becomes byte-for-byte
identical with those generated with current code.
Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
---
scripts/tags.sh | 34 ++++++++++++++++++++++++++++++++--
1 file changed, 32 insertions(+), 2 deletions(-)
--- a/scripts/tags.sh
+++ b/scripts/tags.sh
@@ -152,7 +152,24 @@ dogtags()
exuberant()
{
- all_target_sources | xargs $1 -a \
+ NR_CPUS=1
+ if [ -e /proc/cpuinfo ]; then
+ NR_CPUS=$(grep -e '^processor : ' /proc/cpuinfo | wc -l)
+ fi
+
+ rm -f .make-tags.src.* .make-tags.*
+
+ all_target_sources >.make-tags.src
+ # seems like Useless Use of cat(1) but not really
+ NR_LINES=$(cat .make-tags.src | wc -l)
+ NR_LINES=$((($NR_LINES + $NR_CPUS - 1) / $NR_CPUS))
+
+ split -a 6 -d -l $NR_LINES .make-tags.src .make-tags.src.
+
+ for i in .make-tags.src.*; do
+ N=$(echo $i | sed -e 's/.*\.//')
+ # -u: don't sort now, sort later
+ cat $i | xargs $1 -a -f .make-tags.$N -u \
-I __initdata,__exitdata,__initconst, \
-I __cpuinitdata,__initdata_memblock \
-I __refdata,__attribute,__maybe_unused,__always_unused \
@@ -211,7 +228,20 @@ exuberant()
--regex-c='/DEFINE_PCI_DEVICE_TABLE\((\w*)/\1/v/' \
--regex-c='/(^\s)OFFSET\((\w*)/\2/v/' \
--regex-c='/(^\s)DEFINE\((\w*)/\2/v/' \
- --regex-c='/DEFINE_HASHTABLE\((\w*)/\1/v/'
+ --regex-c='/DEFINE_HASHTABLE\((\w*)/\1/v/' \
+ &
+ done
+ wait
+ rm -f .make-tags.src .make-tags.src.*
+
+ # write header
+ $1 -f tags /dev/null
+ # remove header
+ for i in .make-tags.*; do
+ sed -i -e '/^!/d' $i
+ done
+ sort .make-tags.* >>tags
+ rm -f .make-tags.*
all_kconfigs | xargs $1 -a \
--langdef=kconfig --language-force=kconfig \
next reply other threads:[~2015-04-14 17:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 17:20 Alexey Dobriyan [this message]
2015-04-14 20:05 ` [PATCH] tags: much faster, parallel "make tags" Randy Dunlap
2015-04-14 20:24 ` Guenter Roeck
2015-04-15 9:36 ` Michal Marek
2015-04-15 9:38 ` Michal Marek
2015-04-15 9:51 ` Alexey Dobriyan
2015-04-15 13:24 ` Michal Marek
2015-04-15 13:41 ` Michal Marek
2015-04-15 19:45 ` [PATCH v2] " Alexey Dobriyan
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=20150414172047.GA5641@p183.telecom.by \
--to=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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).