Searched full:competing (Results 1 – 25 of 34) sorted by relevance
12
285 * so it is possible that this flow is competing with in chd_ack_received()293 * not competing with loss based flows at the moment. in chd_ack_received()364 * than qthresh, assume that we are competing with loss based in chd_cong_signal()408 * competing with loss based flows from the start. in chd_conn_init()
333 * Initialise the shadow_cwnd in case we are competing with loss based in cdg_conn_init()657 * falling. Assume we are competing with in cdg_ack_received()668 * Resync shadow window in case we are competing with a in cdg_ack_received()
4 there are no competing masters to consider for gates and therefore there is
16 there are no competing masters to consider for gates and therefore there is
57 competing with loss-based TCP flows.
41 It attempts to maintain fairness when competing with legacy NewReno TCP in lower
40 It attempts to maintain fairness when competing with legacy NewReno TCP in lower
371 as presently implemented are not suitable when users are competing for
127 assert(Raw != getNull() && "Expected non-null from competing generator"); in loadOrGenerate()
178 available space amongst the competing needs. How this
34 // competing with the other, and subsequent instances from having to detect the
557 * competing for ALQ resources. in alq_writen()753 * sleeping here competing for ALQ resources. in alq_getn()
123 // Obj-C Classes represent multiple symbols that could have competing in updateLinkageForSymbols()
133 * competing threads trying to write to the same syslog resource. (On136 * context in the same program competing for syslog's attention. Thus
84 of an advantage over competing non-free programs. These disadvantages
506 All the competing processes would then wake
53 only as secure as you make them, and security concerns are ever competing
1775 "Competing reset task didn't finish. Try again later.\n"); in nvme_ctrlr_suspend()
599 * presence of competing traffic, MAC protocols etc.
1837 * competing for it. So we set s=0, which is not very in ipfw_config_pipe()
674 More recently, competing political groups might disagree about
657 + * by competing threads in the client. The client provides fuctions
6223 * Be aware there are two competing views of "field number": we in xo_gettext_rebuild_content()
995 * protect this. This is ok, since if competing folks call this we in sctp_fill_random_store()