Date: Thu, 29 Nov 2001 10:05:34 -0600 From: Jonathan Lemon <jlemon@flugsvamp.com> To: =?iso-8859-1?Q?=BCB=BEJ=C2=D7?= <cfliu@realtek.com.tw> Cc: Jonathan Lemon <jlemon@flugsvamp.com>, freebsd-net@freebsd.org Subject: Re: Does 4.4 FreeBSD kernel supports TCP simultaneous open? Message-ID: <20011129100534.Q75389@prism.flugsvamp.com> In-Reply-To: <001701c178a3$e43670e0$a22314ac@RTCN3848> References: <200111290637.fAT6bd213755@prism.flugsvamp.com> <001701c178a3$e43670e0$a22314ac@RTCN3848>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 29, 2001 at 03:03:04PM +0800, ¼B¾JÂ× wrote: > Thanks...I know where my problem is now...It's indeed a duplicate SYN. > > By the way, the tcp_input function is so long and large and there are > several goto statements which make reading the code even more difficult. Is > this intened to be like this? Even with Steven's TCP/IP Vol.2, it took me > three whole days to draw a Visio flow chart of this function. Has anybody > ever considered of reorganizing this module? I don't believe so; the code was originally designned to avoid function calls, and is essentially a couple of large switch statements. The flow pretty much mirrors the original RFC, and shouldn't be too hard to follow. I'd be leery of rewriting the code just for the sake of rewriting; chances would be pretty good that you'd introduce a subtle bug in one way or the other. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011129100534.Q75389>