Hello -
In the description of ca_pend_event in the Channel Access Reference Manual,
it says that a very short timeout such as 0.0001 seconds will result in a
"poll". It appears that on my VAX/VMS system, this "poll" really takes
around 10 milliseconds since the VAX time resolution is only to the
nearest 10 msecs. Has anybody ever looked into changing ca_pend_event
so that it truly does a poll (at least on the VAX)?
We are using the EZCA routines on the VAX. When not in a group, the first
thing every EZCA routine does is a ca_pend_event with a 0.00001 sec timeout.
I'm trying to understand why it does a ca_pend_event with a short timeout
instead of a ca_flush_io - can anybody explain?
We have a few applications that do not use EZCA groups (ie, one application
posts many monitors (ezcaSetMonitor) and then periodically gets current
values using non-grouped ezcaGets at different time intervals - ezcaDelay
is periodically called as suggested in the EZCA primer). I thought
we could stand the overhead of the extra polling, but obviously not with the
10 msec wait. In this particular application, it's tough to group the
ezcaGet calls. (OK, Bob Dalesio - you can tell me "I told you so" - go ahead,
make my day!).
-- Stephanie Allison [email protected]
- Navigate by Date:
- Prev:
[no subject] Matt Bickley
- Next:
Re: BURT available on Alpha/Unix platform, but a few problems watson
- Index:
1994
<1995>
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
[no subject] Matt Bickley
- Next:
Re: ca_pend_event question (VAX/VMS only) Jeff Hill
- Index:
1994
<1995>
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|