Lines Matching refs:it

20 You must initialize the kref after you allocate it.  To do this, call
36    it can be passed to another thread of execution, you must
37    increment the refcount with kref_get() before passing it off:
47    holding a valid pointer, it is safe to do this without
51    without already holding a valid pointer, it must serialize access
55 For example, if you allocate some data and then pass it to another
98 This way, it doesn't matter what order the two threads handle the
100 any more and releasing it.  The kref_get() does not require a lock,
121 bad style.  Don't do it.
124 For instance, if you are done with an object and enqueuing it for
125 something else or passing it off to something else, there is no reason
142 and kref_get() it.  That violates rule 3 because you are not already
183 kfree() with the lock held in the example above (since it is kind of
205 preferred as it is a little neater.
249 it's important that kref_get_unless_zero is enclosed in the same critical
252 Note that it is illegal to use kref_get_unless_zero without checking its
256 The function kref_get_unless_zero also makes it possible to use rcu