Lines Matching refs:how

337  * Here we have various control parameters on how
341 * the way fill-cw interacts with timely and caps how much
481 static int32_t rack_ctor(void *mem, int32_t size, void *arg, int32_t how);
1153 "If doing dynamic pacing, how many measurements must be in before we start pacing?");
1175 "By how many time_betweens should we boost the pacing time if we see a ENOBUFS?");
1220 "If the rates between software and hardware match precisely how many extra time_betweens do we get?");
1303 "Rack timely how many times do we push up with b/w increase");
1308 "Rack timely how many times do we push back on b/w decent");
1406 "Does reorder detection fade, if so how many microseconds (0 means never)");
2331 * how long it is until we hit the deadline.
2357 * Now ideally we want to use the end_seq to figure out how much more
2372 * The hard way, figure out how much is gone and then
3637 * we also handle here by calculating how long that time
4279 * counts from there for how long between. But it is
5961 * and this just is not how a policer works.
6147 rack_exit_recovery(struct tcpcb *tp, struct tcp_rack *rack, int how)
7660 * how much is left in original rsm. Then we walk out the mbuf
7786 * need to figure out how to force a full MSS segment out.
8725 * (based on segsiz) and based on how many times its been retransmitted
8758 * (based on segsiz) and based on how many times its been retransmitted
9618 * not sure how :)
10890 * out how far and then sometimes modify that to be
11382 * We keep track of how many DSACK blocks we get
14899 * how rack does retransmissions. Note this
15768 * is left (in which case rack_init() now knows how
16614 * Note how we could move up these in the determination
17648 * we also want to track how many cycles we burned. Note
18367 * Calculate how long this will take to drain, if
18446 * and how much data we put in each packet. Yes this
18903 * We don't know how long we may have been
18983 * We don't have that much in the SB, how much is
19309 * and 0 is empty. So how best to make this into
19948 * we know how many more bytes needs to be sent (presumably either
19950 * the max-burst). We have how much to send and all the info we
20299 /* For fast output no retrans so just inflight and how many mss we send */
21440 * do we need to pace for i.e. how long
21745 * the receive buffer, no matter how small, causes a window update
25537 * Beta is the congestion control value for NewReno that influences how
25545 * Beta_ecn is the congestion control value for NewReno that influences how
25858 rack_ctor(void *mem, int32_t size, void *arg, int32_t how)