linux-2.6.33/rcu_read_lock()
をテンプレートにして作成
[
トップ
] [
新規
|
一覧
|
検索
|
最終更新
|
ヘルプ
|
ログイン
]
開始行:
*参照元 [#lfdbe9d7]
#backlinks
*説明 [#yc8eadef]
-パス: [[linux-2.6.33/include/linux/rcupdate.h]]
-FIXME: これは何?
--説明
**引数 [#l244819b]
-なし
**返り値 [#k087571f]
-なし
**参考 [#pa7408de]
*実装 [#odbf3fc2]
/**
* rcu_read_lock - mark the beginning of an RCU read-sid...
*
* When synchronize_rcu() is invoked on one CPU while ot...
* are within RCU read-side critical sections, then the
* synchronize_rcu() is guaranteed to block until after ...
* CPUs exit their critical sections. Similarly, if cal...
* on one CPU while other CPUs are within RCU read-side ...
* sections, invocation of the corresponding RCU callbac...
* until after the all the other CPUs exit their critica...
*
* Note, however, that RCU callbacks are permitted to ru...
* with RCU read-side critical sections. One way that t...
* is via the following sequence of events: (1) CPU 0 en...
* read-side critical section, (2) CPU 1 invokes call_rc...
* an RCU callback, (3) CPU 0 exits the RCU read-side cr...
* (4) CPU 2 enters a RCU read-side critical section, (5...
* callback is invoked. This is legal, because the RCU ...
* section that was running concurrently with the call_r...
* therefore might be referencing something that the cor...
* callback would free up) has completed before the corr...
* RCU callback is invoked.
*
* RCU read-side critical sections may be nested. Any d...
* will be deferred until the outermost RCU read-side cr...
* completes.
*
* It is illegal to block while in an RCU read-side crit...
*/
static inline void rcu_read_lock(void)
{
__rcu_read_lock();
-
--[[linux-2.6.33/__rcu_read_lock()]]
__acquire(RCU);
-
--[[linux-2.6.33/__acquire()]]
rcu_read_acquire();
-
--[[linux-2.6.33/rcu_read_acquire()]]
}
*コメント [#j6763a27]
終了行:
*参照元 [#lfdbe9d7]
#backlinks
*説明 [#yc8eadef]
-パス: [[linux-2.6.33/include/linux/rcupdate.h]]
-FIXME: これは何?
--説明
**引数 [#l244819b]
-なし
**返り値 [#k087571f]
-なし
**参考 [#pa7408de]
*実装 [#odbf3fc2]
/**
* rcu_read_lock - mark the beginning of an RCU read-sid...
*
* When synchronize_rcu() is invoked on one CPU while ot...
* are within RCU read-side critical sections, then the
* synchronize_rcu() is guaranteed to block until after ...
* CPUs exit their critical sections. Similarly, if cal...
* on one CPU while other CPUs are within RCU read-side ...
* sections, invocation of the corresponding RCU callbac...
* until after the all the other CPUs exit their critica...
*
* Note, however, that RCU callbacks are permitted to ru...
* with RCU read-side critical sections. One way that t...
* is via the following sequence of events: (1) CPU 0 en...
* read-side critical section, (2) CPU 1 invokes call_rc...
* an RCU callback, (3) CPU 0 exits the RCU read-side cr...
* (4) CPU 2 enters a RCU read-side critical section, (5...
* callback is invoked. This is legal, because the RCU ...
* section that was running concurrently with the call_r...
* therefore might be referencing something that the cor...
* callback would free up) has completed before the corr...
* RCU callback is invoked.
*
* RCU read-side critical sections may be nested. Any d...
* will be deferred until the outermost RCU read-side cr...
* completes.
*
* It is illegal to block while in an RCU read-side crit...
*/
static inline void rcu_read_lock(void)
{
__rcu_read_lock();
-
--[[linux-2.6.33/__rcu_read_lock()]]
__acquire(RCU);
-
--[[linux-2.6.33/__acquire()]]
rcu_read_acquire();
-
--[[linux-2.6.33/rcu_read_acquire()]]
}
*コメント [#j6763a27]
ページ名: