Lines Matching refs:bucket
49 to choose a hash table bucket, then reads the next hop that this bucket
83 cause bucket allocation change, the wants counts for individual next hops
91 Each bucket maintains a last-used timer. Every time a packet is forwarded
92 through a bucket, this timer is updated to current jiffies value. One
94 amount of time that a bucket must not be hit by traffic in order for it to
104 upkeep changes the next hop that the bucket references to one of the
135 - Single-bucket notifications of the type
143 Some single-bucket notifications are forced, as indicated by the "force"
145 hop associated with the bucket was removed, and the bucket really must be
150 bucket should be migrated, but the HW discovers that the bucket has in fact
153 A second way for the HW to report that a bucket is busy is through the
201 used to request a single bucket. The attributes recognized at get requests
205 ``NHA_ID`` ID of the next-hop group that the bucket belongs to.
206 ``NHA_RES_BUCKET`` A nest that contains attributes specific to bucket.
212 ``NHA_RES_BUCKET_INDEX`` Index of bucket in the resilient table.
229 ``NHA_RES_BUCKET`` A nest that contains attributes specific to bucket.
251 only), each bucket will be considered idle when no traffic hits it for at
255 Changing next-hop weights leads to change in bucket allocation::
261 # ip nexthop bucket show id 10
280 For example, the following will mark bucket 23 in next-hop group 10 as
286 next attempt to migrate a bucket should fail::