Live data from Hacker News

TCP in 30 instructions (1993)

pdl.cmu.edu

11–20 of 41 posts

Re: TCP in 30 instructions (1993)

#11
post #10

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?

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)

#13
post #10

Earlier 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.

There is no need to be sarcastic. tptacek is pointing out that this is only one portion of that protocol. "The entire Internet" and the rest of the protocol are not the same thing. If you've been downvoted or hellbanned, it's not simply because you asked a question.

Re: TCP in 30 instructions (1993)

#14
post #10

Earlier 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.

Here's some very personal advice. This is my opinion, and others won't agree. However, for what it's worth ...

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)

#15
post #2

This 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?

[deleted]

Re: TCP in 30 instructions (1993)

#16
post #2

This 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?

[deleted]

Re: TCP in 30 instructions (1993)

#17
post #10

Earlier 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.

If you honestly think you've been downvoted for "asking a question", take a moment to think about the type of question you asked and the way you asked it.

Re: TCP in 30 instructions (1993)

#19

I 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".

I read those things as sarcasm (e.g. "none of that buffer-overrun-checking garbage") but perhaps there's more to it.

Re: TCP in 30 instructions (1993)

#20
post #2

This 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?

It shows receiving data, it doesn't show anything about sending data including congestion control. It doesn't even show the full TCP receive a packet process since acking a packet is ... in the code. I also don't see anything about the state machine that occurs during connection creation or tear down. etc. Calling what is in the link TCP is about like claiming to describe the entire postal system in three steps(pick up envelope that has been delivered to your mailbox, open envelope, read letter).
Post reply on HN