Searched refs:hitcount (Results 1 – 4 of 4) sorted by relevance
3 -m recent --rcheck --hitcount 8 --name foo --mask 255.255.255.255 --rsource;=;OK4 -m recent --rcheck --hitcount 12 --name foo --mask 255.255.255.255 --rsource;=;OK7 -m recent --rcheck --hitcount 999 --name foo --mask 255.255.255.255 --rsource;;FAIL9 -m recent --rcheck --hitcount 3 --name foo --mask 255.255.255.255 --rsource -m recent --rcheck --hi…10 -m recent --rcheck --hitcount 4 --name foo --mask 255.255.255.255 --rsource -m recent --rcheck --hi…11 -m recent --rcheck --hitcount 8 --name foo --mask 255.255.255.255 --rsource -m recent --rcheck --hi…
52 \fB\-\-hitcount\fP \fIhits\fP58 time frame. The maximum value for the hitcount parameter is given by the
66 atomic_uintptr_t hitcount; member104 atomic_store_relaxed(&race->hitcount, 0); in AddExpectRace()134 atomic_fetch_add(&race->hitcount, 1, memory_order_relaxed); in CheckContains()189 &ExpectRace::hitcount); in PrintMatchedBenignRaces()198 atomic_load_relaxed(&hit_matched[i].hitcount), in PrintMatchedBenignRaces()308 if (atomic_load_relaxed(&race->hitcount) == 0) { in AnnotateFlushExpectedRaces()
351 # Translate the hitcount into valid JSON values.