Lines Matching refs:data
181 * Mailslots provide a mechanism for fast, unreliable unidirectional data
187 * a "unique name" or a "group name". Various data structures, which are
188 * detailed subsequently within this document, flow as the data portion of
209 * SMB: Total data bytes = 33
211 * SMB: Max data bytes = 0
229 * SMB: Transaction data
230 * SMB: Data: Number of data bytes remaining = 33 (0x0021)
233 * Mailslot Write, and the browser data structure is carried as the
234 * Transact data.
235 * The Transaction data begins with an opcode, that signifies the operation
236 * and determines the size and structure of data that follows. This opcode
251 * the Transaction data e.g. a GetBackupListReq browser frame, a
254 * The structures that are sent as the data portion of the Transact SMB are
438 * data. This will limit the number of systems that can be in a
515 * TotalDataCount n Size of data in bytes to write to
517 * Data[ n ] The data to write to the mailslot
536 * SMB: Total data bytes = 33
538 * SMB: Max data bytes = 0
556 * SMB: Transaction data
557 * SMB: Data: Number of data bytes remaining = 33 (0x0021)
574 * TotalDataCount n Size of data in bytes to write to
576 * Data[ n ] The data to write to the mailslot
608 * header so that the data starts on a word boundary.
629 0, /* Max data bytes to return */
912 unsigned char *data;
917 smb_msgbuf_init(&mb, datagram->data, datagram->data_length, 0);
924 &max_data_to_return, /* Max data bytes to return */
945 data = &datagram->data[data_offset];
953 smb_netlogon_receive(datagram, mailbox, data, datalen);
964 message_type = datagram->data[data_offset];