[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1420666401.5947.35.camel@edumazet-glaptop2.roam.corp.google.com>
Date: Wed, 07 Jan 2015 13:33:21 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: Erik Grinaker <erik@...gler.no>
Cc: Yuchung Cheng <ycheng@...gle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
netdev <netdev@...r.kernel.org>
Subject: Re: TCP connection issues against Amazon S3
On Wed, 2015-01-07 at 20:37 +0000, Erik Grinaker wrote:
> I agree. I have contacted Amazon about this, but am not too hopeful
> for a quick fix; they have been promising SACK-support on their
> loadbalancers since 2006, for example.
>
> That said, since this change breaks a service as popular as S3, it
> might be worth reconsidering.
>
Which change are you talking about ? Have you done a bisection to
clearly identify the patch exposing this sender bug ?
We are not going to stick TCP stack to 20th century and buggy peers or
middleboxes, sorry.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists