Home
last modified time | relevance | path

Searched refs:hashtable (Results 1 – 14 of 14) sorted by relevance

/Linux-v4.19/include/linux/
Dhashtable.h52 #define hash_init(hashtable) __hash_init(hashtable, HASH_SIZE(hashtable)) argument
60 #define hash_add(hashtable, node, key) \ argument
61 hlist_add_head(node, &hashtable[hash_min(key, HASH_BITS(hashtable))])
69 #define hash_add_rcu(hashtable, node, key) \ argument
70 hlist_add_head_rcu(node, &hashtable[hash_min(key, HASH_BITS(hashtable))])
99 #define hash_empty(hashtable) __hash_empty(hashtable, HASH_SIZE(hashtable)) argument
/Linux-v4.19/tools/include/linux/
Dhashtable.h49 #define hash_init(hashtable) __hash_init(hashtable, HASH_SIZE(hashtable)) argument
57 #define hash_add(hashtable, node, key) \ argument
58 hlist_add_head(node, &hashtable[hash_min(key, HASH_BITS(hashtable))])
87 #define hash_empty(hashtable) __hash_empty(hashtable, HASH_SIZE(hashtable)) argument
/Linux-v4.19/Documentation/livepatch/
Dshadow-vars.txt11 The implementation introduces a global, in-kernel hashtable that
15 specifically, the parent pointer serves as the hashtable key while the
16 numeric id subsequently filters hashtable queries. Multiple shadow
26 A hashtable references all shadow variables. These references are
46 - search hashtable for <obj, id> pair
49 - search hashtable for <obj, id> pair
55 - add <obj, id> to the global hashtable
58 - search hashtable for <obj, id> pair
64 - add <obj, id> pair to the global hashtable
67 - find and remove a <obj, id> reference from global hashtable
[all …]
/Linux-v4.19/Documentation/
Dsiphash.txt55 DECLARE_HASHTABLE(hashtable, 8);
66 …return &table->hashtable[siphash(input, sizeof(*input), &table->key) & (HASH_SIZE(table->hashtable
126 Do not ever use HalfSipHash except for as a hashtable key function, and only
129 means of mitigating hashtable flooding denial of service attacks.
167 DECLARE_HASHTABLE(hashtable, 8);
178 …return &table->hashtable[hsiphash(input, sizeof(*input), &table->key) & (HASH_SIZE(table->hashtabl…
187 this will not be a problem, as the hashtable lookup isn't the bottleneck. And
/Linux-v4.19/drivers/infiniband/ulp/opa_vnic/
Dopa_vnic_internal.h274 #define vnic_hash_init(hashtable) __hash_init(hashtable, OPA_VNIC_MAC_TBL_SIZE) argument
276 #define vnic_hash_add(hashtable, node, key) \ argument
278 &hashtable[hash_min(key, ilog2(OPA_VNIC_MAC_TBL_SIZE))])
/Linux-v4.19/net/sunrpc/
Dauth.c26 struct hlist_head *hashtable; member
335 new->hashtable = kcalloc(hashsize, sizeof(new->hashtable[0]), GFP_KERNEL); in rpcauth_init_credcache()
336 if (!new->hashtable) in rpcauth_init_credcache()
411 head = &cache->hashtable[i]; in rpcauth_clear_credcache()
439 kfree(cache->hashtable); in rpcauth_destroy_credcache()
560 hlist_for_each_entry_rcu(entry, &cache->hashtable[nr], cr_hash) { in rpcauth_lookup_credcache()
593 hlist_for_each_entry(entry, &cache->hashtable[nr], cr_hash) { in rpcauth_lookup_credcache()
602 hlist_add_head_rcu(&cred->cr_hash, &cache->hashtable[nr]); in rpcauth_lookup_credcache()
/Linux-v4.19/fs/afs/
Dxdr_fs.h90 __be16 hashtable[AFS_DIR_HASHTBL_SIZE]; member
/Linux-v4.19/fs/affs/
Damigaffs.h54 __be32 hashtable[1]; member
Daffs.h18 #define AFFS_GET_HASHENTRY(data,hashkey) be32_to_cpu(((struct dir_front *)data)->hashtable[hashkey])
/Linux-v4.19/tools/perf/util/
Dauxtrace.c1334 struct hlist_head *hashtable; member
1362 c->hashtable = ht; in auxtrace_cache__new()
1385 hlist_for_each_entry_safe(entry, tmp, &c->hashtable[i], hash) { in auxtrace_cache__drop()
1400 free(c->hashtable); in auxtrace_cache__free()
1422 hlist_add_head(&entry->hash, &c->hashtable[hash_32(key, c->bits)]); in auxtrace_cache__add()
1435 hlist = &c->hashtable[hash_32(key, c->bits)]; in auxtrace_cache__lookup()
/Linux-v4.19/Documentation/networking/
Dnf_flowtable.txt21 The flowtable uses a resizable hashtable, lookups are based on the following
Dscaling.txt200 Per-flow rate is calculated by hashing each packet into a hashtable
/Linux-v4.19/Documentation/media/kapi/
Dv4l2-controls.rst68 handler is expected to handle. It will allocate a hashtable based on this
/Linux-v4.19/Documentation/trace/
Dhistogram.rst115 are in terms of hashtable entries - if a run uses more entries than