Lines Matching refs:structure

52 within a data structure (possibly by replacing them with references to
56 either the old or the new version of the data structure rather than a
58 (e.g., freeing) the data items removed from the data structure during the
74 a.	Remove pointers to a data structure, so that subsequent
81 	to the data structure, so it now may safely be reclaimed
89 prevent an updater from deleting the data structure out from under them.
94 and replacement of data items in a linked structure without disrupting
141 	read-side critical sections.  Any RCU-protected data structure
224 	given structure becomes accessible to other CPUs.  That said,
257 	RCU-protected structure, using the local variable is of
355 global pointer to a dynamically allocated structure.  More-typical
370 	 * with "new_a".  Points gbl_foo to the new structure, and
371 	 * frees up the old structure after a grace period.
374 	 * see the initialized version of the new structure.
377 	 * have references to the old structure complete before freeing
378 	 * the old structure.
398 	 * structure.  Use rcu_read_lock() and rcu_read_unlock()
399 	 * to ensure that the structure does not get deleted out
401 	 * we see the initialized version of the structure (important
432 	RCU-protected data structure, but -before- reclaiming/freeing
457 have an rcu_head structure added, perhaps as follows:
471 	 * with "new_a".  Points gbl_foo to the new structure, and
472 	 * frees up the old structure after a grace period.
475 	 * see the initialized version of the new structure.
478 	 * references to the old structure complete before freeing the
479 	 * old structure.
521 	RCU-protected data structure in order to register a callback
527 kfree() on the structure, you can use kfree_rcu() instead of call_rcu()
663 So, suppose that we remove a data item from its structure and then invoke