Kate Feng wrote:
Is it less confusing if EPICS/vxWorks, EPICS/RTEMS and EPICS/other O.S.
can unify this implementation ? Perhaps, the vxWorks implementation
could be helpful, although could'nt be ideal ? I do not have vxWorks for
3.14 to verify this. However, here is some of my thoughts, hoping to
hear others.
1) Could the vxWorks implementation be ported to the RTEMS as a default ?
Perhaps, that function could be turned off as an option, although not safe,
in case of demanding application assuming the users have absloutely
knowledge and control of the client access of the IOC
I believe that the new RTEMS version of malloc_free_space() is efficient
enough that the connect rates should be acceptable with the existing
implementation of osiSufficentSpaceInPool().
--
Eric Norum [email protected]
Advanced Photon Source Phone: (630) 252-4793
Argonne National Laboratory
- References:
- CA Connect rates under RTEMS wnolan
- Re: CA Connect rates under RTEMS Eric Norum
- Re: CA Connect rates under RTEMS (vxWorks, too) Kate Feng
- Navigate by Date:
- Prev:
Re: CA Connect rates under RTEMS (vxWorks, too) Kate Feng
- Next:
RE: CA Connect rates under RTEMS (vxWorks, too) 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
- Navigate by Thread:
- Prev:
Re: CA Connect rates under RTEMS (vxWorks, too) Kate Feng
- Next:
RE: CA Connect rates under RTEMS (vxWorks, too) 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
|