Lines Matching refs:hash
217 * A hash calculated over an IP version 4 header as follows:
229 * A hash calculated over an IP version 4 header and TCP header as
244 * A hash calculated over an IP version 6 header as follows:
256 * A hash calculated over an IP version 6 header and TCP header as
278 * Toeplitz hash:
306 uint64_t hash = 0;
320 hash ^= prefix;
333 /* The valid part of the hash is in the upper 32 bits. */
334 return hash >> 32;
412 * This is sent by the frontend to set the desired hash algorithm.
436 * This is sent by the frontend to query the types of hash supported by
450 * data = supported hash types (if operation was successful)
452 * NOTE: A valid hash algorithm must be selected before this operation can
458 * This is sent by the frontend to set the types of hash that the backend
459 * should calculate. (See above for hash type definitions).
460 * Note that the 'maximal' type of hash should always be chosen. For
461 * example, if the frontend sets both IPV4 and IPV4_TCP hash types then
462 * the latter hash type should be calculated for any TCP packet and the
482 * NOTE: A valid hash algorithm must be selected before this operation can
490 * This is sent by the frontend to set the key of the hash if the algorithm
491 * requires it. (See hash algorithms above).
515 * zero will clear the key (which ensures that the calculated hash
542 * not supported (i.e. hash mapping is done only by modular
569 * NOTE: Setting data[0] to 0 means that hash mapping should be done
576 * hash value to queue number. The backend should calculate the hash from
826 * alg: The algorithm used to calculate the hash (one of
861 #define XEN_NETIF_EXTRA_TYPE_HASH (4) /* u.hash */
895 } hash;