Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020 
<== Date ==> <== Thread ==>

Subject: RE: CA Connect rates under RTEMS
From: "Jeff Hill" <johill@lanl.gov>
To: "'Eric Norum'" <norume@aps.anl.gov>, <wnolan@bnl.gov>, <tech-talk@aps.anl.gov>
Date: Tue, 18 Jan 2005 12:07:47 -0700
> 
> BTW - the vxWorks implementation of osiSufficentSpaceInPool is of
> questionable
> usefulness so it's not really clear to me that there's any point in
> using this
> routine at all (Jeff Hill disagrees with me on this.....).
> 

My position is that it's a good idea on limited resource OS (i.e. no page
file) to try to keep at least N bytes free in pool, or a maximum free block
larger than N, and to try to prevent the CA server from using all available
memory. This is the justification for the osiSufficentSpaceInPool interface.
Whether you like it or not will depend on personal priority for robustness.

I don't disagree that so far we have not encountered a limited resource OS
that has managed to provide efficient access to such information, but that
issue IMHO is orthogonal with the justification mentioned in the previous
paragraph.

I don't doubt that a brilliant OS designer will stumble onto a solution
eventually, and until that time comes we may have to settle for a function
that always return true on certain OS, or for polling the function less
frequently (an admittedly less than satisfactory compromise). It would of
course also help to allocate *all* memory off of free lists, but this is not
easy especially with any approach to variable length strings that requires
contiguous storage.

Jeff 



References:
Re: CA Connect rates under RTEMS Eric Norum

Navigate by Date:
Prev: Re: CA Connect rates under RTEMS Eric Norum
Next: Re: CA Connect rates under RTEMS Till Straumann
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020 
Navigate by Thread:
Prev: Re: CA Connect rates under RTEMS Eric Norum
Next: Re: CA Connect rates under RTEMS (vxWorks, too) Kate Feng
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·