Earlier quoted context omitted.
Well, TCP is a very simple protocol so I can't imagine what the OP means by "all of TCP" unless he's talking about IP and it's associated services.
Because TCP is very simple, you can't imagine that "all of TCP" means what it actually says? Huh?
TCP in 30 instructions (1993)
11–20 of 41 posts
Re: TCP in 30 instructions (1993)
#12Re: TCP in 30 instructions (1993)
#13Earlier quoted context omitted.
Because TCP is very simple, you can't imagine that "all of TCP" means what it actually says? Huh?
You guys are just to smart for me, I guess I'll have to withdraw from having any conversation at all since I've been downvoted into hellban for asking a question.
Re: TCP in 30 instructions (1993)
#14Earlier quoted context omitted.
Because TCP is very simple, you can't imagine that "all of TCP" means what it actually says? Huh?
You guys are just to smart for me, I guess I'll have to withdraw from having any conversation at all since I've been downvoted into hellban for asking a question.
I would suggest that you would benefit from learning how to ask questions. Here's a start:
http://www.catb.org/~esr/faqs/smart-questions.html
However, there's more advice than that, and that, although a good start, is not to be taken as gospel. You probably also should read the site-specific commentary, and suggested alternatives:
https://mikeash.com/getting_answers.html
https://news.ycombinator.com/item?id=2911381
The point is this - you said:
Well, TCP is a very simple protocol so I can't imagine
what the OP means by "all of TCP" unless he's talking
about IP and it's associated services.
Here's an alternative: I'm not sure I understand what's been left out of this.
Could someone provide a synopsis, and a pointer to more
details?
Your comment comes across as "Well I know everything, so the only thing that's left out must be all the internet." The second admits that you don't know what people are talking about, and asks for more information.And just as a final question - why do you think you've been hell-banned? Are you sure? In particular, I've turned on "Show dead", and you don't seem to have made any comments that have been auto-killed. The evidence suggests you are not hell-banned.
Re: TCP in 30 instructions (1993)
#15This is a very famous post, and Van Jacobsen is the archetypical networking systems programming bad-ass. Important context here though: this is just the per-segment receive processing piece of TCP; it's describing a very simple fast path that segments can take, but not all the TCP logic!
Wouldn't "all the TCP logic" be the entire internet?
Re: TCP in 30 instructions (1993)
#16This is a very famous post, and Van Jacobsen is the archetypical networking systems programming bad-ass. Important context here though: this is just the per-segment receive processing piece of TCP; it's describing a very simple fast path that segments can take, but not all the TCP logic!
Wouldn't "all the TCP logic" be the entire internet?
Re: TCP in 30 instructions (1993)
#17Earlier quoted context omitted.
Because TCP is very simple, you can't imagine that "all of TCP" means what it actually says? Huh?
You guys are just to smart for me, I guess I'll have to withdraw from having any conversation at all since I've been downvoted into hellban for asking a question.
Re: TCP in 30 instructions (1993)
#18Re: TCP in 30 instructions (1993)
#19I love the opinionated writing style. I wish I knew more about this so I could relate to the comments about the "compiler braindamage", "mbuf chain stupidity", and "netipl software interrupt bs".
Re: TCP in 30 instructions (1993)
#20This is a very famous post, and Van Jacobsen is the archetypical networking systems programming bad-ass. Important context here though: this is just the per-segment receive processing piece of TCP; it's describing a very simple fast path that segments can take, but not all the TCP logic!
Wouldn't "all the TCP logic" be the entire internet?