| 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 <2019> 2020 2021 2022 2023 2024 2025 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 <2019> 2020 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Misleading "initPeriodic: Scan rate ... is not achievable" and sleep quantum implementation |
| From: | Michael Davidsaver via Core-talk <[email protected]> |
| To: | "Johnson, Andrew N." <[email protected]>, "[email protected]" <[email protected]> |
| Date: | Wed, 24 Jul 2019 13:08:00 -0700 |
On 7/24/19 1:02 PM, Johnson, Andrew N. via Core-talk wrote: > I don't think anyone has suggested using clock_getres() for the quantum value before; that might be a better solution than just returning zero. Anyone else want to weigh in on that idea — should we just apply Dirk's patch? cf. the posix version of epicsMonotonicResolution() I've never looked at what is returned for CLOCK_REALTIME (which is always present). I think the ultimate fallback has to be returning zero. 1e-3 is too arbitrary.