Re: FAST_LOCK and R3.14

[Eric Norum <norume@aps.anl.gov>]

In many cases that's going to slow your driver down more than  
necessary.  Here are the notes from the vxWorks->OSI conversion  
document:

http://www.aps.anl.gov/epics/wiki/index.php/ 
How_to_make_your_EPICS_driver_operating_system_independent

You’ll have to use your judgement here. If the section of code
being protected is ‘quick’ (less than a few microseconds) it’s rea-
sonable to simply disable interrupts while the code is active. In
this case you can remove the ‘lock’ variable and the init/free
operations and then add a local ‘key’ variable and replace the
lock/unlock operations with epicsInterruptLock/Unlock opera-
tions. If the section of code being protected is longer you’ll have
to convert the FASTLOCK to an EPICS mutex.


On Oct 19, 2006, at 10:52 AM, Dirk Zimoch wrote:

> Hi all
>
> I have to convert some drivers from 3.13 to 3.14.
>
> Is it save (and recommended) to replace FAST_LOCK with epicsMutex ?
>
> Dirk
>
> --
> Dr. Dirk Zimoch
> Swiss Light Source
> Computing and Controls
> Paul Scherrer Institut
> phone +41 56 310 5182
> fax   +41 56 310 4413

--
Eric Norum <norume@aps.anl.gov>
Advanced Photon Source
Argonne National Laboratory
(630) 252-4793