Lines Matching defs:data
95 * If there is any inconsistency in the XenStore data, the backend may
164 * significant amount of out-of-band data to be passed from frontend to
165 * backend. Use of xenstore is not suitable for large quantities of data
267 * This algorithm uses a 'key' as well as the data buffer itself.
329 * | id | type | data[0] |
331 * | data[1] | data[2] |
336 * data[]: any data associated with the request (determined by type)
352 uint32_t data[3];
365 * | data |
371 * data: any data associated with the response (determined by type and
385 uint32_t data;
400 * data[0] = a XEN_NETIF_CTRL_HASH_ALGORITHM_* value
401 * data[1] = 0
402 * data[2] = 0
412 * NOTE: Setting data[0] to XEN_NETIF_CTRL_HASH_ALGORITHM_NONE disables
425 * data[0] = 0
426 * data[1] = 0
427 * data[2] = 0
433 * data = supported hash types (if operation was successful)
451 * data[0] = bitwise OR of XEN_NETIF_CTRL_HASH_TYPE_* values
452 * data[1] = 0
453 * data[2] = 0
463 * data = 0
467 * Also, setting data[0] to zero disables hashing and the backend
479 * data[0] = grant reference of page containing the key (assumed to
481 * data[1] = size of key in octets
482 * data[2] = 0
493 * data = 0
515 * data[0] = 0
516 * data[1] = 0
517 * data[2] = 0
523 * data = maximum number of entries allowed in the mapping table
540 * data[0] = number of entries in mapping table
541 * data[1] = 0
542 * data[2] = 0
550 * data = 0
552 * NOTE: Setting data[0] to 0 means that hash mapping should be done
567 * data[0] = grant reference of page containing the mapping (sub-)table
569 * data[1] = size of (sub-)table in entries
570 * data[2] = offset, in entries, of sub-table within overall table
582 * data = 0
604 * invalidate any table data outside that range.
643 * tx request data (xen_netif_tx_request_t)
740 * NOTE: Because extra info data overlays the usual request/response
754 * |type |flags| type specific data |
818 /* Packet data has been validated against protocol checksum. */
898 /* Packet data has been validated against protocol checksum. */