1 / 54

제목 : TCP Input

제목 : TCP Input. 2005. 6. 13( 월 ) 한 민 규 icemk@mclab.hufs.ac.kr. Introduction Preliminary Processing Header Prediction ACK Processing. Content. Introduction. The tcp_input function is called by ipintr when a datagram is received with a protocol field of TCP. Introduction (Con’t).

duante
Télécharger la présentation

제목 : TCP Input

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 제목 : TCP Input 2005. 6. 13(월) 한 민 규 icemk@mclab.hufs.ac.kr

  2. Introduction Preliminary Processing Header Prediction ACK Processing Content

  3. Introduction • The tcp_input function is called by ipintr when a datagram is received with a protocol field of TCP

  4. Introduction (Con’t) Introduction normal flow slow path   Fast path • Validate the input segment & locate the PCB for this connection • The term drop means to drop the segmentbeing processed, not drop the connection,but when an RST is sent by dropwithreset itit normally causes the connection to be dropped

  5. Preliminary Processing • Declarations and preliminary processing If the number of bytes in the first mbuf in the chain is less than the size of the combined IP/TCP header(40bytes), m_pullup moves the first 40 bytes into thefirst mbuf. Convert data pointer of tcpiphdr * tcp statistic value

  6. Preliminary Processing tlen is the TCP length, the number of bytes following the IP header Dataoffset : 4bit로 구성된 dataoffset 항목은 32bit word. 즉 한 bit가 4byte를 나타내어 TCP 헤더의 전체 길이를 표시한다.

  7. Preliminary Processing The benefit in recognizing the timestamp optionthis way is to avoid calling the general option processing function tcp_dooptions later in the code If all three conditions are true, ts_present is set to 1

  8. Preliminary Processing The two 16-bit port numbers are left in network byte order TCP maintains a one-behind cache(tcp_last_inpcb) conaining the address of the PCB for the last recevied TCP segment If the PCB was not found, the input segment is dropped and an RST is sent as a reply IF the PCB exists but a corresponding TCP control block does not exist, the socket is probably being closed, so the input segment is dropped and an RST is sent as a reply

  9. Preliminary Processing tcp_saveti : These become arguments to tcp_trace when it is called at the end of the function Socket has had listen() When a segment arrives for a listening socket , a new socket is created by sonewconn Compute window scale factor RFC793 window size 16bit : 64k  extend (scale option with SYN)

  10. Preliminary Processing t_idle is set to 0 since a segment has been received on the connection. The keep-alive timer is also reset to 2hours If options are present in the TCP header, and if the connection state is not LISTEN, tcp_dooptions processes the options

  11. tcp_dooptions Function MSS Option: If the length is not 4(TCPOLEN_MAXSEG), or the segment does not have the SYN flag set, the option is ignored Window scale Option

  12. Header Prediction 1. Check if segment is the next expected The connection state musth be ESTABLISHED SYN,FIN,RST, or URG control flags must not be on ts_val > ts_recent ti_seq ==rcv_nxt tiwin(adv window) must be nonzero snd_nxt must equal the highest sequence number sent(snd_max) 2. If a timestamp option is present, Update ts_recent from received timestamp • Header prediction helps unidirectional data transfer by handling the two common cases. • If TCP is sending data, the next expected segment for this connection is an ACK for outstanding data. • If TCP is sending data, the next expected segment for this connections is the next in-sequence data segment •  Faster then the general processing

  13. Header Prediction Update RTT estimators Delete acknowledged bytes from send buffer Stop retransmit timer ??? Awaken waiting process : If a process must be awakened when the send buffer is modified

  14. Header Prediction

  15. TCP input: Slow Path Processing We continue with the code that’s executed if header prediction fails, the slow path through tcp_input. win is set to he number of bytes available in the socket’s receive buffer Receive window setting

  16. Initiation of Passive Open, Completion of Active Open If the state is LISTEN or SYN_SENT, expected segment in these two states is a SYN, and we’ll see that any other received segment is dropped Drop if RST, ACK, or no SYN

  17. Initiation of Passive Open, Completion of Active Open TCP is defined only for unicast applications. Recall that the M_BCAST and M_MCAST flags wre set by ether_input, based on the destination hardware address of the frame • Get mbuf for client’s IP address and port • Set local address in PCB • Connect PCB to peer

  18. Complete processing of SYN received in LISTEN state Initialize sequence number variables in control block • TF_ACKNOW flag is set since the ACK of a SYN is not delayed • The connection state becomes SYN_RCVD • The connection-establishment timer is set to 75 seconds(TCPTV_KEEP_INIT) •  tcp_output will be called

  19. Completion of Active Open TCP is expecting to receive a SYN Acceptable ACK and RST • tcp_sendseqinit sets all four of these variables to 365 • tcp_sendseqinit sets all four of these variables to 365

  20. Process received SYN in response to an active open Active Open complete • Since data can arrive for a connection befoe the connection is • established, any such data is now placed in the receive by calling tcp_reass • If the SYN that is ACKed was being timed, tcp_xmit_timer initializes the RTT estimators based on the measured RTT • for the SYN • Simultaneous Open

  21. Simultaneous open • If it is greater than the receive winodw, the excess data is dropped by m_adj()

  22. PAWS:Protecion Against Wrapped Sequence Numbers

  23. Trim Segment so Data is Within Window • These data bytes have already been acknowledged and passed to the applications • duplicate data at the beginning of the received segment is discarded • Data that is beyond the end of the window is discarded from the end of the segment

  24. Handle completely duplicate segment ti_seq rcv_nxt This normally ocuurs when the other end did not receive our ACK, causing the other end to retransmit the segment.

  25. Handle data that arrives after the process terminates • If the socket has no descriptor referencing it, the process has closed t he connection • The segment is then dropped and an RST is output

  26. Calculate number of bytes beyond right edge of window • todrop would be (6+5) – (4+6) = 1

  27. Reomove data beyond right edge of window • Check for new incarnation of a connection in the TIME_WAIT state • - the SYN flag is set, • - the connection is in the TIME_WAIT state • - the new starting sequence number is greater then the final sequence number for the connection • This is allowed by RFC 1122, • - the ISS for the new connection must be • greater than the last sequence number • used(rcv_nxt). TCP adds 128,000(TCP_ISSNCR), which becomes the ISS • check for pobe of closed window • Drop other segments that are completely outside • window • The data to the right of the window is discarded • from the mbuf chain by m_adj and ti_len is updated

  28. When to Drop an Ack • In an actual scenario, when both ends of a connection had a hole in the data on the reassembly • queue and both ends enter the persist state, the connection becomes deadlocked as both ends • throw away perfectly good ACKs

  29. Self-Connects and Simultaneous Opens

  30. Record Timestamp

  31. Process RST flag • SYN_RCVD state • - Normally it is entered from the LISTEN state • - This state can also be entered by a simultaneous • open, after a process has called connect • The other end sent its SYN and then terminated before the reply arrived, causing it to end an RST • This state can also be entered by a simultaneous open, after a process has called connect • Other states - The receipt of an RST in the ESTABLISHED, • FIN_WAIT1, FIN_WAIT2, or CLOSE_WAIT states • returns the error ECONNRESET

  32. ACK Processing

  33. Received ACK in SYN_RCVD state Available wndsize Accept, select snd_una snd_max ti_ack

  34. Fast Retransmit and Fast Recovery • The fast retransmit algorithm occurs when TCP deduces from a small number (normally 3) of consecutive duplicate ACKs that a segment has been lost and deduces the starting sequence number of the missing segment • The fast recovery algorithm says that after the fast retransmit algorithm (that is, after the missing segment has been retransmitted), congestion avoidance but not slow start is performed

  35. Check for completely duplicate ACK • snd_una < acknowledgment field <= snd_max

  36. Duplicate ACK processing Set congestion window Set snd_nxt Number of consecutive duplicate ACKS exceeds threshold of 3 • t_dupacks equals 3(tcprexmtthresh). Congestion avoidance is performed and the missing segment is retransmitted • t_dupacks exceeds 3. Increase the congestion window and perform normal TCP output • t_dupacks is less than 3. Do nothing.

  37. Value of cwnd and send sequence while data is being transmitted

  38. ACK Processing Congestion window reset Check for out-of-range ACK (Acceptable ACK)

  39. RTT measurements and retransmission timer Base on Delayed-ACK ts_ecr : timestamp echo reply needoutput : 1 This flag forces a call to tcp_output at the end of this function

  40. Open congestion window in response to ACKs

  41. Remove acknowledged data from send buffer /* actual chars in buffer */ Reomve from the send buffer

  42. Receipt of ACK in FIN_WAIT_1 state 한쪽 호스트에서 연결 종료과정 초기의 FIN-ACK 세그먼트가 전송된 상태

  43. Receipt of ACK in CLOSING state FIN-ACK가 수신되었지만 이에 대한 ACK는 전송되지 않은상태. Simultaneous close 상태

  44. Receipt of ACK in LAST_ACK state 수신된 FIN-ACK에 대한 ACK의 전송

  45. Receipt of ACK in TIME_WAIT state 양 호스트의 TCP가 FIN-ACK와 이에 대한 응답을 교환하고 TCP 연결종료 과정을 마무리한 상태. 이 상태가 되면 Maximum segment lifetime(Default 120초)의 두배의 시간동안 기다렸다가 해당 연결의 포트번호를 다시 사용할 수 있다.

  46. Update window information Needoutput is set to 1 since the new value of snd_wnd might enable a segment to be sent • snd_w11 records the sequence number of the last segment used to update the send window • snd_w12 records the acknowledgement number of the last segment used to update the send window ti_seq snd_w11 snd_w12 ti_seq snd_w11 ti_ack snd_wnd snd_wnd snd_una snd_nxt snd_una snd_nxt

  47. Urgent mode processing • URG flag is ignored in the CLOSE_WAIT, CLOSING, LAST_ACK, or TIME_WAIT state • If the urgent offset plus the number of bytes already in the receive buffer exceeds the maximum size of a socket buffer

  48. Processing of received urgent pointer A new urgent pointer has been received

  49. Place out-of-band byte into t_iobc

  50. Merge received data into sequencing queue for socket

More Related