[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20091116.191522.178198674.davem@davemloft.net>
Date: Mon, 16 Nov 2009 19:15:22 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: eric.dumazet@...il.com
Cc: william.allen.simpson@...il.com, netdev@...r.kernel.org,
joe@...ches.com
Subject: Re: [net-next-2.6 PATCH v6 4/7 RFC] TCPCT part 1d: define TCP
cookie option, extend existing struct's
From: Eric Dumazet <eric.dumazet@...il.com>
Date: Mon, 16 Nov 2009 23:26:04 +0100
> So adding DATA to SYN packets might be problematic for part of our tcp stack.
I can almost guarentee it won't work. For one thing getting a SACK
response to a SYN+DATA packet will explode quite nicely for one thing.
A lot of the other retransmit queue handling would need to be audited
as well. So much code assumes that if we see sent data in the
retransmit queue, there won't be SYN or SYN+ACK things in there to
contend with.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists