From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: Johannes Sixt <j.sixt@viscovery.net>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v2] git daemon: avoid waking up too often
Date: Wed, 23 Jul 2008 20:39:56 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0807232038310.8986@racer> (raw)
In-Reply-To: <32541b130807231226m73fcc874ub72f69adeb5d26c3@mail.gmail.com>
Hi,
On Wed, 23 Jul 2008, Avery Pennarun wrote:
> On 7/23/08, Johannes Sixt <j.sixt@viscovery.net> wrote:
> > This makes porting this beast to Windows practically impossible
> > because we cannot have a poll() implementation that waits both on a
> > listening socket and a pipe. :-(
>
> I have worked around such problems in the past by having a thread whose
> job it is to read from the pipe and simply write it to a socket. The
> trick works for "console" objects, too, which in win32 are even less
> agreeable than pipes.
>
> (In case your life wasn't disgusting enough already today :))
Thanks. I thought the code I looked at today was ugly, but you convinced
me that there is no limit.
> Alternatively, you could use something like socketpair() instead of a
> pipe for this purpose. Naturally, Win32 helps you out here by somehow
> forgetting to include socketpair() in winsock, although it's sort of
> easy to emulate.
Or alternatively, you could read my response to Hannes where I explain
that the pipe() is not even needed with threaded start_async() (as opposed
to fork()ed one).
Ciao,
Dscho
prev parent reply other threads:[~2008-07-23 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 21:52 [PATCH] git daemon: avoid waking up too often Johannes Schindelin
2008-07-22 22:03 ` [PATCH v2] " Johannes Schindelin
2008-07-23 6:51 ` Johannes Sixt
2008-07-23 9:17 ` Johannes Schindelin
2008-07-23 19:26 ` Avery Pennarun
2008-07-23 19:39 ` Johannes Schindelin [this message]
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=alpine.DEB.1.00.0807232038310.8986@racer \
--to=johannes.schindelin@gmx.de \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
/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