From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: kusmabite@gmail.com, git@vger.kernel.org,
"Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: What's cooking in git.git (Feb 2011, #07; Mon, 28)
Date: Wed, 02 Mar 2011 07:49:51 +0100 [thread overview]
Message-ID: <4D6DE88F.9030001@viscovery.net> (raw)
In-Reply-To: <7voc5uenmy.fsf@alter.siamese.dyndns.org>
Am 3/1/2011 18:50, schrieb Junio C Hamano:
> Erik Faye-Lund <kusmabite@gmail.com> writes:
>> There's also the added complication that _open_osfhandle also seems to
>> be limited by this 2048 limit (see the third comment here:
>> http://bugs.mysql.com/bug.php?id=24509). We use this function for
>> pipes and sockets as well. This alone might be a reason to corner-case
>> test the resulting binary on Windows properly.
>
> As long as the use of osfhandles for non filedescriptors is reasonably
> bounded, it may be enough to make the 25 slop configurable per platform,
> no?
It's not necessary to complicate things. The file descriptors acquired
with _open_osfhandle are (only) used in the implementation of pipe() and
socket() and count towards the limit no more and no less than the file
descriptors acquired with pipe() and socket() on Unix.
-- Hannes
next prev parent reply other threads:[~2011-03-02 6:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 1:05 What's cooking in git.git (Feb 2011, #07; Mon, 28) Junio C Hamano
2011-03-01 7:59 ` Jens Lehmann
2011-03-01 8:39 ` Erik Faye-Lund
2011-03-01 17:50 ` Junio C Hamano
2011-03-02 6:49 ` Johannes Sixt [this message]
2011-03-02 18:22 ` Erik Faye-Lund
2011-03-02 18:28 ` Erik Faye-Lund
2011-03-05 17:04 ` Michael J Gruber
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=4D6DE88F.9030001@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kusmabite@gmail.com \
--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).