| 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: [Merge] ~dirk.zimoch/epics-base:epicsMutexPriorityInheritance into epics-base:7.0 |
| From: | Dirk Zimoch via Core-talk <core-talk at aps.anl.gov> |
| To: | mdavidsaver <mdavidsaver at gmail.com> |
| Date: | Tue, 24 Nov 2020 10:17:27 -0000 |
> Also, what is the motivation to economize pthread_mutexattr_t? I see > __SIZEOF_PTHREAD_MUTEXATTR_T==4 (on a 64-bit host). It's simply not necessary that each mutex creates its own attribute. >From the pthread_mutexattr_init manual page: "After a mutex attributes object has been used to initialize one or more mutexes, any function affecting the attributes object (including destruction) shall not affect any previously initialized mutexes." Thus the same attribute can be used for all mutexes and the mutex does not use it any more after creation. It is a waste of not only space but also time and error handling complexity to have (and keep!) one in each mutex. -- https://code.launchpad.net/~dirk.zimoch/epics-base/+git/epics-base/+merge/394327 Your team EPICS Core Developers is subscribed to branch epics-base:7.0.