CK_RHS_STAT(3)
π ck_rhs_stat β bestie, let's get that hash set status π
okay so this page lives in the CK_RHS_STAT(3) manual, and it's brought to you by the Concurrency Kit β that's libck, you link it with -lck. π
πΈ NAME πΈ
ck_rhs_stat β get hash set status. she's nosy, she wants the receipts, and honestly? valid. π
π LIBRARY π
Concurrency Kit (that's libck, and yes you pass -lck when you're building). π§
β¨ SYNOPSIS β¨
#include <ck_rhs.h>
void
ck_rhs_stat(ck_rhs_t *hs, struct ck_rhs_stat *st);
π¦ DESCRIPTION π¦
so ck_rhs_stat(3) is literally just a lil gossip session with your hash set. it takes all the juicy statistics and stores them in the object that st points at. no cap. π«Ά
and the ck_rhs_stat structure is defined like this, exactly:
struct ck_rhs_stat {
unsigned long n_entries; /* Current number of keys in hash set. */
unsigned int probe_maximum; /* Longest read-side probe sequence. */
};
so n_entries is how many keys are in the hash set right now β like, the current headcount. and probe_maximum is the longest read-side probe sequence, which is giving "how far did we have to dig to find someone" energy. iconic. π
π RETURN VALUES π
ck_rhs_stat(3) has no return value. void. nothing. she gives you stats and then she's gone, main character exit. π
π ERRORS π
okay bestie, listen up because this part is not a vibe:
- behavior is undefined if
hsis uninitialized. do not do that. do not pass me an uninitialized hash set. π - behavior is undefined if this function is called by a non-writer thread. like, writer threads only, periodt. don't be the friend who tries it from the wrong thread. π
fr fr, "undefined behavior" is not cute. it's the "we literally cannot tell you what happens" tier. respect the writer-thread rule. π
π SEE ALSO π
ck_rhs_init(3)ck_rhs_move(3)ck_rhs_destroy(3)CK_RHS_HASH(3)ck_rhs_iterator_init(3)ck_rhs_next(3)ck_rhs_get(3)ck_rhs_put(3)ck_rhs_put_unique(3)ck_rhs_set(3)ck_rhs_fas(3)ck_rhs_remove(3)ck_rhs_grow(3)ck_rhs_gc(3)ck_rhs_rebuild(3)ck_rhs_count(3)ck_rhs_reset(3)ck_rhs_reset_size(3)
and if you want even more, the additional information is available at http://concurrencykit.org/ π β go read, it's giving β¨ research era β¨.
that's the whole page, babe. this one's dated September 17, 2012 and it's the CK_RHS_STAT(3) manual β mwah, sending you off with stats and good vibes only. ππΈβ¨
π¦ where this page comes from
- alpine 3.24: ck-doc 0.7.2-r1 Β· BSD-2-Clause AND Apache-2.0
- debian bookworm: libck-dev 0.7.1-10 Β· BSD-2-Clause
- debian trixie: libck-dev 0.7.2-6 Β· BSD-2-Clause
- epel 10: ck-devel 0.7.2-1.el10_1 Β· BSD-2-clause AND Apache-2.0 AND BSD-3-clause
- epel 9: ck-devel 0.7.0-10.el9 Β· BSD
- fedora 43: ck-devel 0.7.2-2.fc43 Β· BSD-2-clause AND Apache-2.0 AND BSD-3-clause
- fedora 43: ck-devel 0.7.2-2.fc43 Β· BSD-2-clause AND Apache-2.0 AND BSD-3-clause
- fedora 44: ck-devel 0.7.2-4.fc44 Β· BSD-2-clause AND Apache-2.0 AND BSD-3-clause
- fedora 44: ck-devel 0.7.2-4.fc44 Β· BSD-2-clause AND Apache-2.0 AND BSD-3-clause
- nixos 26.05: ck 0.7.2
- nixpkgs unstable: ck 0.7.2
- opensuse-leap 16.0: ck-devel 0.7.2-bp160.1.9 Β· Apache-2.0 AND BSD-2-Clause
- opensuse-leap 16.0: ck-devel 0.7.2-bp160.1.9 Β· Apache-2.0 AND BSD-2-Clause
- opensuse-leap 16.0: ck-devel 0.7.2-bp160.1.9 Β· Apache-2.0 AND BSD-2-Clause
- ubuntu jammy: libck-dev 0.7.1-6ubuntu2 Β· BSD-2-Clause
- ubuntu noble: libck-dev 0.7.1-13build1 Β· BSD-2-Clause
- ubuntu questing: libck-dev 0.7.2-5ubuntu1
- ubuntu resolute: libck-dev 0.7.2-5ubuntu2 Β· BSD-2-Clause
- ubuntu stonking: libck-dev 0.7.2-11 Β· BSD-2-Clause
- Copyright 2012-2013 Samy Al Bahra
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms