From: "Marco Costalba" <mcostalba@gmail.com>
To: "Andreas Ericsson" <ae@op5.se>
Cc: "Shawn Pearce" <spearce@spearce.org>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: Fast access git-rev-list output: some OS knowledge required
Date: Fri, 8 Dec 2006 19:34:44 +0100 [thread overview]
Message-ID: <e5bfff550612081034q5e4c0c93s3512fce2f11b1fab@mail.gmail.com> (raw)
In-Reply-To: <45781639.1050208@op5.se>
On 12/7/06, Andreas Ericsson <ae@op5.se> wrote:
> Shawn Pearce wrote:
> >
> > Perhaps there is some fast IPC API supported by Qt that you could
> > use to run the revision listing outside of the main UI process,
> > to eliminate the bottlenecks you are seeing and remove the problems
> > noted above? One that doesn't involve reading from a pipe I mean...
> >
>
> Why not just fork() + exec() and read from the filedescriptor? You can
> up the output buffer of the forked program to something suitable, which
> means the OS will cache it for you until you copy it to a buffer in qgit
> (i.e., read from the descriptor).
>
Please, what do you mean with "something suitable"? How can I redirect
the output to a memory buffer or to a file that the OS will cache
*until* I've copied it?
If I redirect to a 'normal' file, this will be flushed by OS after
some time, normally few seconds.
Could you please post links with examples/docs about this kind of
implementation?
Thanks
next prev parent reply other threads:[~2006-12-08 18:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 19:24 Fast access git-rev-list output: some OS knowledge required Marco Costalba
2006-12-06 19:28 ` Shawn Pearce
2006-12-06 19:34 ` Marco Costalba
2006-12-06 19:42 ` Shawn Pearce
2006-12-06 19:51 ` Shawn Pearce
2006-12-06 20:08 ` Marco Costalba
2006-12-06 20:18 ` Shawn Pearce
2006-12-07 13:25 ` Andreas Ericsson
2006-12-07 14:53 ` Johannes Schindelin
2006-12-07 15:28 ` Andreas Ericsson
2006-12-07 16:01 ` Johannes Schindelin
2006-12-08 18:34 ` Marco Costalba [this message]
2006-12-08 20:10 ` Michael K. Edwards
2006-12-09 12:15 ` Marco Costalba
2006-12-06 23:27 ` Johannes Schindelin
2006-12-07 0:47 ` Linus Torvalds
2006-12-07 6:46 ` Marco Costalba
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=e5bfff550612081034q5e4c0c93s3512fce2f11b1fab@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).