From: "Marco Costalba" <mcostalba@gmail.com>
To: "Linus Torvalds" <torvalds@osdl.org>
Cc: "Git Mailing List" <git@vger.kernel.org>,
"Junio C Hamano" <junkio@cox.net>,
"Alex Riesen" <raa.lkml@gmail.com>,
"Shawn Pearce" <spearce@spearce.org>
Subject: Re: [RFC \ WISH] Add -o option to git-rev-list
Date: Mon, 11 Dec 2006 18:39:44 +0100 [thread overview]
Message-ID: <e5bfff550612110939r58df1a73ud28983633c12e487@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0612110905180.12500@woody.osdl.org>
On 12/11/06, Linus Torvalds <torvalds@osdl.org> wrote:
>
>
> On Mon, 11 Dec 2006, Linus Torvalds wrote:
> >
> > That's not timing what I asked. That's just timing the "git-rev-list". You
> > need to time the "cat" part too. Either use a script, or do something like
> >
> > time sh -c "git-rev-list ... | cat > /dev/null".
>
> Btw, if you do this, you'll actually see one of the _real_ advantages of
> pipes.
>
> On an SMP system, you'll easily get output like "110%CPU", since now the
> git-rev-list and the user can run in parallel. Of course, they can do so
> with temp-files too, but then you have all the "is it a true EOF, or is it
> just the fact that the writer hasn't written everything yet" problem (and
> the _normal_ solution for that is to simply not allow any overlapping
> work).
>
Sorry for wrong data, I will repost as soon as I can.
Regarding the _normal_ solution we have one more hipotesys to take
advantage of: git-rev-list when has nothing more to read..exits.
This is what lead to the exit loop condition based on git-rev-list is
still alive, instead of messing with an EOF.
eof = (no more data && !rev_list_is_running);
With this we could enter the loop one more time then necessary, but
nothing else bad should happen.
next prev parent reply other threads:[~2006-12-11 17:39 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-10 11:38 [RFC \ WISH] Add -o option to git-rev-list Marco Costalba
2006-12-10 14:54 ` Alex Riesen
2006-12-10 18:16 ` Linus Torvalds
2006-12-10 19:51 ` Marco Costalba
2006-12-10 20:00 ` globs in partial checkout? Michael S. Tsirkin
2006-12-10 20:13 ` Linus Torvalds
2006-12-10 21:07 ` Michael S. Tsirkin
2006-12-10 20:08 ` [RFC \ WISH] Add -o option to git-rev-list Linus Torvalds
2006-12-10 20:19 ` Linus Torvalds
2006-12-10 22:05 ` Marco Costalba
2006-12-10 22:09 ` Marco Costalba
2006-12-10 22:16 ` Linus Torvalds
2006-12-10 22:35 ` Marco Costalba
2006-12-10 22:53 ` Linus Torvalds
2006-12-11 0:15 ` Marco Costalba
2006-12-11 0:51 ` Linus Torvalds
2006-12-11 7:17 ` Marco Costalba
2006-12-11 10:00 ` Alex Riesen
2006-12-11 16:59 ` Linus Torvalds
2006-12-11 17:07 ` Linus Torvalds
2006-12-11 17:39 ` Marco Costalba [this message]
2006-12-11 18:15 ` Linus Torvalds
2006-12-11 18:59 ` Marco Costalba
2006-12-11 19:25 ` Linus Torvalds
2006-12-11 20:28 ` Josef Weidendorfer
2006-12-11 20:40 ` Linus Torvalds
2006-12-11 20:54 ` Josef Weidendorfer
2006-12-11 21:14 ` Linus Torvalds
2006-12-15 18:45 ` Marco Costalba
2006-12-15 19:20 ` Linus Torvalds
2006-12-15 20:41 ` Marco Costalba
2006-12-15 21:04 ` Marco Costalba
2006-12-11 9:26 ` Josef Weidendorfer
2006-12-11 12:52 ` Marco Costalba
2006-12-11 13:28 ` Josef Weidendorfer
2006-12-11 17:28 ` Marco Costalba
2006-12-11 11:39 ` Andreas Ericsson
2006-12-11 12:59 ` Marco Costalba
2006-12-11 13:40 ` Andreas Ericsson
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=e5bfff550612110939r58df1a73ud28983633c12e487@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=raa.lkml@gmail.com \
--cc=spearce@spearce.org \
--cc=torvalds@osdl.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).