Hi, Quick Description: Question: Example:
(this happens for a ~30 minutes until the buffer returns to max and starts dropping again). asked 21 Mar '14, 06:59 blablabla edited 21 Mar '14, 07:36 |
One Answer:
PSH does not mean "don't buffer this", it means "don't buffer this and wait for more before sending the buffer content to the applicatiuon layer". The TCP needs to put the incoming bytes somewhere before passing it on to the application, but when the push flag is set the stack is not allowed to wait for more data before it passes it on. So I guess it is normal that you have a 11 byte drop in the Window size. It should go up again in the next ACK though, but maybe the stack doesn't see the need as long as it has a lot of window bytes left for buffering more. It may be saying "I'll raise my window later, why bother now" :-) The important thing is a) the incoming bytes needs to be buffered to be able to pass them on; there is no direct pipeline that bypasses buffering (at least as far as I know) b) Window size is not a problem unless it slows down the receiving of more incoming data, which in your case doesn't seem to be the problem. answered 21 Mar '14, 10:12 Jasper ♦♦ edited 21 Mar '14, 10:13 |