Lines Matching defs:data
48 * data segments.
49 * Andi Kleen: Make sure we never ack data there is not
89 #define FLAG_DATA 0x01 /* Incoming frame contained data. */
91 #define FLAG_DATA_ACKED 0x04 /* This ACK acknowledged new data. */
98 #define FLAG_ORIG_SACK_ACKED 0x200 /* Never retransmitted data are (s)acked */
250 * more data may not be arriving soon, and yet the data sender
254 * reads all of the data and is not ping-pong. If len > MSS
257 * reads data and there is more than an MSS of unACKed data.
267 len += skb->data - skb_transport_header(skb);
704 * This function should be called every time data is copied to user space.
773 * problem is that "good" TCP's do slow start at the beginning of data
775 * sender will sit on his end and only queue most of his data, because
795 /* The _first_ data packet received, initialize
826 /* Called to compute a smoothed rtt estimate. The data fed to this
990 /* Take a notice that peer is sending D-SACKs. Skip update of data delivery
1277 /* D-SACK for already forgotten data... Do dumb counting. */
2054 /* Account for ACK, ACKing some data in Reno Recovery phase. */
2257 * amount of SACKed data. Even without SACKs
2560 /* Try to undo cwnd reduction, because D-SACKs acked all retransmitted data */
2809 /* Process an ACK in CA_Loss state. Move to CA_Open if lost data are
2823 /* Step 3.b. A timeout is spurious if not all data are
2824 * lost, i.e., never-retransmitted data are (s)acked.
2835 /* Step 2.b. Try send new data (but deferred until cwnd
2854 /* A Reno DUPACK means new data in F-RTO step 2.b above are
3080 * Karn's algorithm forbids taking RTT if some retransmitted data
3088 * acknowledges some new data, i.e., only if it advances the
3298 * true data, and if we misinform our callers that
3299 * this ACK acks real data, we will erroneously exit
3389 /* Do not re-arm RTO if the sack RTT is measured from data sent
3463 /* If reordering is high then always grow cwnd whenever data is
3683 /* TLP of new data has been acknowledged */
3791 /* If the ack includes data we haven't sent yet, discard
3860 * "When the TCP data sender is ready to set the CWR bit after reducing
3862 * new data packet that it transmits."
3868 /* We passed data and got it acked, remove any soft error
3914 /* If data was DSACKed, see if we can undo a cwnd reduction. */
3931 /* If data was SACKed, tag it and see if we should send more data.
3932 * If data was DSACKed, see if we can undo a cwnd reduction.
4207 /* If not enough data remaining, we can short cut */
4248 * [ Later note. Even worse! It is buggy for segments _with_ data. RFC
4249 * states that events when retransmit arrives after original data are rare.
4289 * of data (and SYN, FIN, of course) is checked separately.
4705 /* This one checks to see if we can put data from the
5019 /* Queue data for delivery to the user.
5179 * - bloated or contains data before "start" or
5224 /* Copy data, releasing collapsed skbs. */
5360 * until the socket owning process reads some of the data
5397 * drop receive data on the floor. It will get retransmitted
5540 /* We sent a data segment already. */
5547 * This routine is only called when we have urgent data
5550 * place. We handle URGent data wrong. We have to - as
5565 /* Ignore urgent data that we've already seen and read. */
5574 * such data and will stay in TCP_URG_NOTYET until will be eaten
5589 /* We may be adding urgent data when the last byte read was
5592 * as data, nor can we alter copied_seq until this data arrives
5600 * only in this artificial test. Insert some normal data between A and B and we will
5630 /* Do we wait for any urgent data? - normally not... */
5743 * and no data has been received
5785 * - Urgent data is expected.
5802 const struct tcphdr *th = (const struct tcphdr *)skb->data;
5866 /* Bulk data transfer: sender */
5916 /* Bulk data transfer: receiver */
5961 /* Process urgent data. */
6024 /* Prevent spurious tcp_cwnd_restart() on first data
6042 struct sk_buff *data = tp->syn_data ? tcp_rtx_queue_head(sk) : NULL;
6061 * acknowledges data. Presumably the remote received only
6063 * SYN-data or the corresponding SYN-ACK was dropped.
6065 syn_drop = (cookie->len < 0 && data);
6076 if (data) { /* Retransmit unacked data in SYN */
6081 skb_rbtree_walk_from(data) {
6082 if (__tcp_retransmit_skb(sk, data, 1))
6093 /* SYN-data is counted as two separate packets in tcp_ack() */
6329 /* Note, we could accept data and URG from this segment.
6331 * either change tcp_recvmsg() to prevent it from returning data
6334 * However, if we ignore data in ACKless segments sometimes,
6338 * Uncomment this return to process the data.
6382 /* Re-arm the timer because data may have been sent out.
6383 * This is similar to the regular data transmission case
6384 * when new data has just been ack'ed.
6387 * retransmitting any data sooner based on when they
6520 /* Prevent spurious tcp_cwnd_restart() on first data packet */
6614 /* RFC 793 says to queue data in these states,
6802 saved_syn = kmalloc(struct_size(saved_syn, data, len),
6808 memcpy(saved_syn->data, base, len);