From: Junio C Hamano <gitster@pobox•com>
To: Eric Wong <normalperson@yhbt•net>
Cc: git@vger•kernel.org
Subject: Re: [PATCH] attempt connects in parallel for IPv6-capable builds
Date: Thu, 28 Jan 2016 19:04:34 -0800 [thread overview]
Message-ID: <xmqqtwlxjdbx.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160128115720.GA1827@dcvr.yhbt.net> (Eric Wong's message of "Thu, 28 Jan 2016 11:57:21 +0000")
Eric Wong <normalperson@yhbt•net> writes:
> getaddrinfo() may return multiple addresses, not all of which
> are equally performant. In some cases, a user behind a non-IPv6
> capable network may get an IPv6 address which stalls connect().
I'd assume that you are not solving a hypothetical problem, but you
may (at least sometimes) have to reach outside world from such a
network environment. I further assume that git_tcp_connect() is not
the only activity you do from such a network, and other network
activities are similarly affected.
How do you work around the same issue for connections that do not go
through git_tcp_connect()? The same issue would affect Git traffic
going over git-remote-curl, and also your usual Web browser traffic,
no?
What I am getting at is if it is saner to solve the issue like how
curl(1) solves it with its -4/-6 command line options, e.g. by
adding a pair of configuration variables "net.ipv[46] = true/false".
next prev parent reply other threads:[~2016-01-29 3:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 11:57 [PATCH] attempt connects in parallel for IPv6-capable builds Eric Wong
2016-01-28 23:42 ` Junio C Hamano
2016-01-29 1:41 ` Eric Wong
2016-01-29 7:10 ` Johannes Sixt
2016-01-29 3:04 ` Junio C Hamano [this message]
2016-01-29 6:08 ` Torsten Bögershausen
2016-01-30 13:09 ` Eric Wong
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=xmqqtwlxjdbx.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=normalperson@yhbt$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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