diff options
| -rw-r--r-- | Documentation/DocBook/kernel-locking.tmpl | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/Documentation/DocBook/kernel-locking.tmpl b/Documentation/DocBook/kernel-locking.tmpl index e6cc57460212..ed64d220baf2 100644 --- a/Documentation/DocBook/kernel-locking.tmpl +++ b/Documentation/DocBook/kernel-locking.tmpl | |||
| @@ -1645,7 +1645,9 @@ the amount of locking which needs to be done. | |||
| 1645 | all the readers who were traversing the list when we deleted the | 1645 | all the readers who were traversing the list when we deleted the |
| 1646 | element are finished. We use <function>call_rcu()</function> to | 1646 | element are finished. We use <function>call_rcu()</function> to |
| 1647 | register a callback which will actually destroy the object once | 1647 | register a callback which will actually destroy the object once |
| 1648 | the readers are finished. | 1648 | all pre-existing readers are finished. Alternatively, |
| 1649 | <function>synchronize_rcu()</function> may be used to block until | ||
| 1650 | all pre-existing are finished. | ||
| 1649 | </para> | 1651 | </para> |
| 1650 | <para> | 1652 | <para> |
| 1651 | But how does Read Copy Update know when the readers are | 1653 | But how does Read Copy Update know when the readers are |
| @@ -1714,7 +1716,7 @@ the amount of locking which needs to be done. | |||
| 1714 | - object_put(obj); | 1716 | - object_put(obj); |
| 1715 | + list_del_rcu(&obj->list); | 1717 | + list_del_rcu(&obj->list); |
| 1716 | cache_num--; | 1718 | cache_num--; |
| 1717 | + call_rcu(&obj->rcu, cache_delete_rcu, obj); | 1719 | + call_rcu(&obj->rcu, cache_delete_rcu); |
| 1718 | } | 1720 | } |
| 1719 | 1721 | ||
| 1720 | /* Must be holding cache_lock */ | 1722 | /* Must be holding cache_lock */ |