public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: "Pádraig Brady" <P@draigBrady.com>
Cc: akpm@linux.foundation.org, mmarek@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] tags: much faster, parallel "make tags"
Date: Sun, 10 May 2015 16:26:34 +0300	[thread overview]
Message-ID: <20150510132633.GA1717@p183.telecom.by> (raw)
In-Reply-To: <554D9606.7090908@draigBrady.com>

On Sat, May 09, 2015 at 06:07:18AM +0100, Pádraig Brady wrote:
> On 08/05/15 14:26, Alexey Dobriyan wrote:

> >  exuberant()
> >  {
> > -	all_target_sources | xargs $1 -a                        \
> > +	rm -f .make-tags.*
> > +
> > +	all_target_sources >.make-tags.src
> > +	NR_CPUS=$(getconf _NPROCESSORS_ONLN 2>/dev/null || echo 1)
> 
> `nproc` is simpler and available since coreutils 8.1 (2009-11-18)

nproc was discarded because getconf is standartized.

> > +	NR_LINES=$(wc -l <.make-tags.src)
> > +	NR_LINES=$((($NR_LINES + $NR_CPUS - 1) / $NR_CPUS))
> > +
> > +	split -a 6 -d -l $NR_LINES .make-tags.src .make-tags.src.
> 
> `split -d -nl/$(nproc)` is simpler and available since coreutils 8.8 (2010-12-22)

-nl/ can't count and always make first file somewhat bigger, which is
suspicious. What else it can't do right?

> > +	sort .make-tags.* >>$2
> > +	rm -f .make-tags.*
> 
> Using sort --merge would speed up significantly?

By ~1 second, yes.

> Even faster would be to get sort to skip the header lines, avoiding the need for sed.
> It's a bit awkward and was discussed at:
> http://lists.gnu.org/archive/html/coreutils/2013-01/msg00027.html
> Summarising that, is if not using merge you can:
> 
>   tlines=$(($(wc -l < "$2") + 1))
>   tail -q -n+$tlines .make-tags.* | LC_ALL=C sort >>$2
> 
> Or if merge is appropriate then:
> 
>   tlines=$(($(wc -l < "$2") + 1))
>   eval "eval LC_ALL=C sort -m '<(tail -n+$tlines .make-tags.'{1..$(nproc)}')'" >>$2

Might as well teach ctags to do real parallel processing.
LC_* are set by top level Makefile.

> p.p.s. You may want to `trap EXIT cleanup` to rm -f .make-tags.*

The real question is how to kill ctags reliably.
Naive

	trap 'kill $(jobs -p); rm -f .make-tags.*' TERM INT

doesn't work.

Files are removed, but processes aren't.

  reply	other threads:[~2015-05-10 13:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 13:26 [PATCH v3] tags: much faster, parallel "make tags" Alexey Dobriyan
2015-05-09  5:07 ` Pádraig Brady
2015-05-10 13:26   ` Alexey Dobriyan [this message]
2015-05-10 13:53     ` Alexey Dobriyan
2015-05-10 20:58     ` Pádraig Brady
2015-05-11 20:20       ` Alexey Dobriyan
2015-05-11 20:25         ` [PATCH v4] " Alexey Dobriyan
2015-08-19 13:25           ` Michal Marek

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=20150510132633.GA1717@p183.telecom.by \
    --to=adobriyan@gmail.com \
    --cc=P@draigBrady.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