summaryrefslogtreecommitdiff
path: root/src/reply-password
diff options
context:
space:
mode:
authorMichal Schmidt <mschmidt@redhat.com>2014-10-14 23:35:24 +0200
committerMichal Schmidt <mschmidt@redhat.com>2014-10-23 17:38:02 +0200
commite4c691b59db60ef2e6d8e64766d6ae02cd0dd457 (patch)
treef6af93bdc6599e642099d3f9fc3a3b3e4ca2aee1 /src/reply-password
parent9700d6980f7c212b10a69399e6430b82a6f45587 (diff)
hashmap: introduce hashmap_reserve()
With the current hashmap implementation that uses chaining, placing a reservation can serve two purposes: - To optimize putting of entries if the number of entries to put is known. The reservation allocates buckets, so later resizing can be avoided. - To avoid having very long bucket chains after using hashmap_move(_one). In an alternative hashmap implementation it will serve an additional purpose: - To guarantee a subsequent hashmap_move(_one) will not fail with -ENOMEM (this never happens in the current implementation).
Diffstat (limited to 'src/reply-password')
0 files changed, 0 insertions, 0 deletions