Lines Matching refs:reference

145    Internally, memory policies are implemented by a reference counted
297 To resolve use/free races, struct mempolicy contains an atomic reference
299 decrement this reference count, respectively.  mpol_put() will only free
300 the structure back to the mempolicy kmem cache when the reference count
303 When a new memory policy is allocated, its reference count is initialized
304 to '1', representing the reference held by the task that is installing the
306 structure, another reference is added, as the task's reference will be dropped
310 on the reference count, as this can lead to cache lines bouncing between cpus
321    BIND policy nodemask is used, by reference, to filter ineligible nodes.
323 We can avoid taking an extra reference during the usages listed above as
329 2) for querying the policy, we do not need to take an extra reference on the
345    potential race, the shared policy infrastructure adds an extra reference
348    reference when we're finished "using" the policy.  We must drop the
349    extra reference on shared policies in the same query/allocation paths
351    as such, and the extra reference is dropped "conditionally"--i.e., only
354    Because of this extra reference counting, and because we must lookup