Searched refs:hit (Results 1 – 9 of 9) sorted by relevance
210 local hit = res:hit()211 if hit then216 local hit = res:hit()217 if not hit then249 local hit = res:hit()250 if hit then255 local hit = res:hit()256 if not hit then
140 if res:hit() == false then147 if res:hit() then
235 if res:hit() then328 if res:hit() then480 if fres == nil or fres:hit() == false then
12 * Items hit at least twice are considered active.27 which are never hit again will flow from HOT, through COLD, and out the28 bottom. Items occasionally active (reaching COLD, but being hit before
82 If a header is hit twice overall, and the second time within ~60s of the first85 instances of an item being hit twice within ~60s it will be recached into
546 - h: return whether item has been hit before as a 0 or 1578 - h: return whether item has been hit before as a 0 or 1581 The above two flags return the value of "hit before?" and "last access time"583 hit or always show an access time of "0" unless combined with the "u" flag.614 of the LRU. This also avoids marking an item as being hit or updating its last655 hit.980 instance has hit its limit. It might be desirable to have memory laid out1405 | evicted_active | 64u | Items evicted from LRU that had been hit |
477 You're not guaranteed a response to a getq/getkq cache hit until you
584 unsigned int hit :1; member
911 unsigned int hit :1; member