icinga2/lib/base/shared-object.hpp
Alexander A. Klimov c8dccd9905 intrusive_ptr_*(): specify memory_order explicitly
More relaxed memory_order = less safety guarantees = faster execution.

This is safe because std::shared_ptr does the same. See also:
https://en.cppreference.com/w/cpp/atomic/memory_order
"Typical use for relaxed memory ordering is incrementing counters, such as the reference counters of std::shared_ptr, since this only requires atomicity, but not ordering or synchronization (note that decrementing the std::shared_ptr counters requires acquire-release synchronization with the destructor)."
2025-04-29 11:41:00 +02:00

74 lines
1.3 KiB
C++

/* Icinga 2 | (c) 2019 Icinga GmbH | GPLv2+ */
#ifndef SHARED_OBJECT_H
#define SHARED_OBJECT_H
#include "base/atomic.hpp"
#include "base/object.hpp"
#include <cstdint>
namespace icinga
{
class SharedObject;
inline void intrusive_ptr_add_ref(SharedObject *object);
inline void intrusive_ptr_release(SharedObject *object);
/**
* Seamless and polymorphistic base for any class to create shared pointers of.
* Saves a memory allocation compared to std::shared_ptr.
*
* @ingroup base
*/
class SharedObject
{
friend void intrusive_ptr_add_ref(SharedObject *object);
friend void intrusive_ptr_release(SharedObject *object);
protected:
inline SharedObject() : m_References(0)
{
}
inline SharedObject(const SharedObject&) : SharedObject()
{
}
inline SharedObject(SharedObject&&) : SharedObject()
{
}
inline SharedObject& operator=(const SharedObject&)
{
return *this;
}
inline SharedObject& operator=(SharedObject&&)
{
return *this;
}
inline virtual
~SharedObject() = default;
private:
Atomic<uint_fast64_t> m_References;
};
inline void intrusive_ptr_add_ref(SharedObject *object)
{
object->m_References.fetch_add(1, std::memory_order_relaxed);
}
inline void intrusive_ptr_release(SharedObject *object)
{
if (object->m_References.fetch_sub(1, std::memory_order_acq_rel) == 1u) {
delete object;
}
}
}
#endif /* SHARED_OBJECT_H */