Lines Matching refs:hash
200 * A hash calculated over an IP version 4 header as follows:
212 * A hash calculated over an IP version 4 header and TCP header as
227 * A hash calculated over an IP version 6 header as follows:
239 * A hash calculated over an IP version 6 header and TCP header as
261 * Toeplitz hash:
289 uint64_t hash = 0;
303 hash ^= prefix;
316 /* The valid part of the hash is in the upper 32 bits. */
317 return hash >> 32;
395 * This is sent by the frontend to set the desired hash algorithm.
419 * This is sent by the frontend to query the types of hash supported by
433 * data = supported hash types (if operation was successful)
435 * NOTE: A valid hash algorithm must be selected before this operation can
441 * This is sent by the frontend to set the types of hash that the backend
442 * should calculate. (See above for hash type definitions).
443 * Note that the 'maximal' type of hash should always be chosen. For
444 * example, if the frontend sets both IPV4 and IPV4_TCP hash types then
445 * the latter hash type should be calculated for any TCP packet and the
465 * NOTE: A valid hash algorithm must be selected before this operation can
473 * This is sent by the frontend to set the key of the hash if the algorithm
474 * requires it. (See hash algorithms above).
498 * zero will clear the key (which ensures that the calculated hash
525 * not supported (i.e. hash mapping is done only by modular
552 * NOTE: Setting data[0] to 0 means that hash mapping should be done
559 * hash value to queue number. The backend should calculate the hash from
809 * alg: The algorithm used to calculate the hash (one of
844 #define XEN_NETIF_EXTRA_TYPE_HASH (4) /* u.hash */
878 } hash;