Re: [PATCH] attempt connects in parallel for IPv6-capable builds

2016-01-30 Thread Eric Wong
Junio C Hamano wrote: > Eric Wong 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 hypoth

Re: [PATCH] attempt connects in parallel for IPv6-capable builds

2016-01-28 Thread Johannes Sixt
Am 29.01.2016 um 02:41 schrieb Eric Wong: Junio C Hamano wrote: Eric Wong 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(). Instead of waiting

Re: [PATCH] attempt connects in parallel for IPv6-capable builds

2016-01-28 Thread Torsten Bögershausen
On 2016-01-29 04.04, Junio C Hamano wrote: > Eric Wong 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

Re: [PATCH] attempt connects in parallel for IPv6-capable builds

2016-01-28 Thread Junio C Hamano
Eric Wong 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

Re: [PATCH] attempt connects in parallel for IPv6-capable builds

2016-01-28 Thread Eric Wong
Junio C Hamano wrote: > Eric Wong 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(). > > Instead of waiting synchronously for a connec

Re: [PATCH] attempt connects in parallel for IPv6-capable builds

2016-01-28 Thread Junio C Hamano
Eric Wong 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(). > Instead of waiting synchronously for a connect() to timeout, use > non-blocking

[PATCH] attempt connects in parallel for IPv6-capable builds

2016-01-28 Thread Eric Wong
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(). Instead of waiting synchronously for a connect() to timeout, use non-blocking connect() in parallel and take