Swiftdiff options
| author | Tobias Markmann <tm@ayena.de> | 2015-11-18 13:51:58 (GMT) |
|---|---|---|
| committer | Swift Review <review@swift.im> | 2015-11-19 15:32:04 (GMT) |
| commit | fcf6a898de9c4f89db5de686aa203b3a52c18029 (patch) | |
| tree | 4df426d92600eba8d4d60a88faaff1d5839129b0 /Swiften/EventLoop/DummyEventLoop.h | |
| parent | cda6fd478b3d8f7f30f771b18324db389a01b1b3 (diff) | |
| download | swift-fcf6a898de9c4f89db5de686aa203b3a52c18029.zip swift-fcf6a898de9c4f89db5de686aa203b3a52c18029.tar.bz2 | |
Redesign event loops to be thread-safe and deterministic
The new event loop design has a single event queue that is
synchronized to protect against data races.
The removal of events in the queue by EventOwner is
deterministic.
Test-Information:
All unit and integration tests with TSAN and
cxxflags=-DBOOST_SP_USE_PTHREADS on Debian 8.2 pass without
reports.
Multiple Swiften/QA/ClientTest/ClientTest runs under
different CPU stress caused no TSAN reports on Debian 8.2.
Swift itself only causes TSAN reports related to Qt itself,
out of our control, and most likely false positives, i.e.
TSAN not detecting the synchronization method inside Qt
correctly.
Unit tests pass without errors and successfully connected
to Slimber on OS X 10.10.5.
Change-Id: Ia1ed32ac2e758c5b9f86e0dac21362818740881e
Diffstat (limited to 'Swiften/EventLoop/DummyEventLoop.h')
| -rw-r--r-- | Swiften/EventLoop/DummyEventLoop.h | 42 |
1 files changed, 8 insertions, 34 deletions
diff --git a/Swiften/EventLoop/DummyEventLoop.h b/Swiften/EventLoop/DummyEventLoop.h index 297549e..b41cd09 100644 --- a/Swiften/EventLoop/DummyEventLoop.h +++ b/Swiften/EventLoop/DummyEventLoop.h @@ -8,8 +8,8 @@ #include <deque> -#include <boost/thread/mutex.hpp> #include <boost/thread/locks.hpp> +#include <boost/thread/mutex.hpp> #include <Swiften/Base/API.h> #include <Swiften/EventLoop/EventLoop.h> @@ -20,40 +20,14 @@ namespace Swift { DummyEventLoop(); virtual ~DummyEventLoop(); - void processEvents() { - while (hasEvents()) { - /* - Creating a copy of the to-be-handled Event object because handling - it can result in a DummyEventLoop::post() call. - This call would also try to lock the eventsMutex_, resulting in a - deadlock. - */ - - eventsMutex_.lock(); - Event eventCopy = events_[0]; - eventsMutex_.unlock(); - - handleEvent(eventCopy); - - { - boost::lock_guard<boost::mutex> lock(eventsMutex_); - events_.pop_front(); - } - } - } - - bool hasEvents() { - boost::lock_guard<boost::mutex> lock(eventsMutex_); - return !events_.empty(); - } - - virtual void post(const Event& event) { - boost::lock_guard<boost::mutex> lock(eventsMutex_); - events_.push_back(event); - } + void processEvents(); + + bool hasEvents(); + + virtual void eventPosted(); private: - boost::mutex eventsMutex_; - std::deque<Event> events_; + bool hasEvents_; + boost::mutex hasEventsMutex_; }; } |