2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: [Merge] ~dirk.zimoch/epics-base:epicsMutexPriorityInheritance into epics-base:7.0 |
From: | mdavidsaver via Core-talk <core-talk at aps.anl.gov> |
To: | mp+394327 at code.launchpad.net |
Date: | Mon, 23 Nov 2020 15:42:31 -0000 |
I see in posix/osdMutex.c that > /* Until these can be demonstrated to work leave them undefined*/ > /* On solaris 8 _POSIX_THREAD_PRIO_INHERIT fails*/ > #undef _POSIX_THREAD_PROCESS_SHARED > #undef _POSIX_THREAD_PRIO_INHERIT has been present since 2002. I would naively think that the various sites using RTLinux flavors which have noticed quickly if epicsMutex didn't have priority inheritance. Can Dirk (or anyone) give some background on why this change is being proposed now? Also, some significant complexity is being added in the !HAVE_RECURSIVE_MUTEX case. Is this implementation actually used by any currently supported targets? -- https://code.launchpad.net/~dirk.zimoch/epics-base/+git/epics-base/+merge/394327 Your team EPICS Core Developers is requested to review the proposed merge of ~dirk.zimoch/epics-base:epicsMutexPriorityInheritance into epics-base:7.0.