Lines Matching defs:send
935 * Call the server routine, and get the reply message to send.
957 * a send-once notification.
1055 * then it isn't sent and the send-once right for the notify
1110 * We do the port send check here instead of in ipc_kmsg_send()
1112 * and we need to do the send check before anything is actually copied.
1157 * make-send or make-sonce, then we must be looking
1160 * copy-send and make-send.
1221 * To make this atomic, just do one copy-send,
1222 * and dup the send right we get out.
1248 * to get two send rights for the price of one.
1271 * To make this atomic, just do a move-send,
1272 * and dup the send right we get out.
1348 * send-once rights (types are both move-sonce) and
1702 * the send operation terminates. Thus if the data
2105 * with the notify port supplying the send-once right.
2147 * The problem is atomically making a send-once right
2152 * and consume send-once rights for the notify port
2155 * to detect that a send-once right has been created
2160 * the send-once right, we lock the notify port,
2194 * send-once right, but we can't release
3079 mach_msg_descriptor_t *sstart, *send;
3106 send = sstart + slist->msgh_descriptor_count;
3130 while (sstart < send) {
3139 if (sstart >= send) {
3459 mach_msg_descriptor_t *saddr, *send;
3465 send = saddr + body->msgh_descriptor_count;
3467 for ( ; saddr < send; saddr++ ) {