Searched refs:urgent (Results 1 - 4 of 4) sorted by relevance
/illumos-gate/usr/src/uts/i86xpv/cpu/generic_cpu/ |
H A D | gcpu_mca_xpv.c | 239 boolean_t urgent) 252 urgent ? XEN_MC_URGENT : XEN_MC_NONURGENT, 238 mctelem_traverse(void *head, enum mctelem_direction direction, boolean_t urgent) argument
|
/illumos-gate/usr/src/uts/common/inet/tcp/ |
H A D | tcp_fusion.c | 298 * urgent data, this can be handled by the regular tcp_rcv_drain(). 299 * If we have urgent data sitting in the receive list, we will 342 * Fusion output routine used to handle urgent data sent by STREAMS based 364 * Each occurence denotes a new urgent pointer. For each new 365 * urgent pointer we signal (SIGURG) the receiving app to indicate 366 * that it needs to go into urgent mode. This is similar to the 367 * urgent data handling in the regular tcp. We don't need to keep 368 * track of where the urgent pointer is, because each T_EXDATA_REQ 369 * "advances" the urgent pointer for us. 371 * The actual urgent dat 444 boolean_t urgent = (DB_TYPE(mp) != M_DATA); local [all...] |
H A D | tcp_output.c | 205 tcp_wput_data(tcp_t *tcp, mblk_t *mp, boolean_t urgent) argument 341 if (urgent) 447 /* usable = MAX(usable, {1 for urgent, 0 for data}) */ 467 * 4. Urgent pointer is not set. Send urgent data ignoring the 468 * Nagle algorithm. This reduces the probability that urgent 657 /* TODO: How should flush interact with urgent data? */ 698 * thing. For another, how should urgent data interact? 1400 * Try to force urgent data out on the wire. Even if we have unsent 1401 * data this will at least send the urgent flag. 3160 * Need to do urgent pointe [all...] |
/illumos-gate/usr/src/cmd/cmd-inet/usr.lib/mdnsd/ |
H A D | mDNSEmbeddedAPI.h | 604 mDNSu16 urgent; variable
|
Completed in 273 milliseconds