From: Michal Marek <mmarek@suse.cz>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tags: much faster, parallel "make tags"
Date: Wed, 15 Apr 2015 15:41:28 +0200 [thread overview]
Message-ID: <552E6A88.4000408@suse.cz> (raw)
In-Reply-To: <552E668A.7090707@suse.cz>
On 2015-04-15 15:24, Michal Marek wrote:
> On 2015-04-14 19:20, Alexey Dobriyan wrote:
>> 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
>
> I wonder if we should rather respect the -j option to make here. But
> then most people probably won't realize that make tags is parallel and
> will not use -j when generating tags. So let's leave it as is.
I meant, leave the concept as is, but fix the detection of the number of
cpus.
>> + # 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
>
> The hardcoded "tags" filename will break 'make TAGS' when using
> exuberant ctags via an 'etags' symlink.
Additionally, the TAGS file must not be sorted.
Michal
next prev parent reply other threads:[~2015-04-15 13:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 17:20 [PATCH] tags: much faster, parallel "make tags" Alexey Dobriyan
2015-04-14 20:05 ` 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 [this message]
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=552E6A88.4000408@suse.cz \
--to=mmarek@suse.cz \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.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