epics/pcas
0
0
Fork 0
Code Issues Pull Requests Projects Wiki Activity

stated that multiple threads are not allowed if preemptive callback is disabled

Browse Source
This commit is contained in:
Jeff Hill
2001-10-15 21:20:58 +00:00
parent f26ba7daa6
commit d67e8a28c6
1 changed files with 12 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
src/ca/CAref.html
View File

@@ -709,7 +709,7 @@ channel access calls.</p>
callbacks might be called when the thread that calls this routine is
not executing in the CA client library. Programmers who are unfamiliar
with mutual exclusion locking in a multi-threaded environment should
specify <code>ca_disable_preemptive_callback.</code></p>
specify <code>ca_disable_preemptive_callback.</code> </p>
</dd>
</dl>
@@ -797,6 +797,11 @@ are made by the application can't be guaranteed, and application programs may
need to be prepared for a connected channel to enter a disconnected state at
any time.</p>
<p>If<code> ca_disable_preemptive_callback </code>is specified then
additional threads are <em>not </em>allowed to join the CA context using
ca_context_attach() because allowing other threads to join implies that CA
callbacks will be called preemptively from more than one thread.</p>
<h4>Arguments</h4>
<dl>
<dt><code>PROCESS_VARIABLE_NAME</code></dt>
@@ -2242,7 +2247,12 @@ returned.</p>
<h4>Description</h4>
<p>Become a member of the specified CA context.</p>
<p>Become a member of the specified CA context. If<code>
ca_disable_preemptive_callback </code>is specified when ca_context_create()
is called ( or if ca_task_initialize() is called ) then additional threads
are <em>not </em>allowed to join the CA context because allowing other
threads to join implies that CA callbacks will be called preemptively from
more than one thread.</p>
<h4>Arguments</h4>
<dl>