X-Git-Url: https://git.netwichtig.de/gitweb/?a=blobdiff_plain;f=include%2Fthreadengine.h;h=964b8d796d0a5c97c36751c68d59c7aa2f90eb62;hb=79892a727e323dcc4bce7e9c0cf3c99c5fe61706;hp=228f817cadd89f07ace5508e9920302a7e13fbd5;hpb=7b6eae36661bc798f69b22393b85a4f06d533cf6;p=user%2Fhenk%2Fcode%2Finspircd.git diff --git a/include/threadengine.h b/include/threadengine.h index 228f817ca..964b8d796 100644 --- a/include/threadengine.h +++ b/include/threadengine.h @@ -1,174 +1,173 @@ -/* +------------------------------------+ - * | Inspire Internet Relay Chat Daemon | - * +------------------------------------+ +/* + * InspIRCd -- Internet Relay Chat Daemon * - * InspIRCd: (C) 2002-2009 InspIRCd Development Team - * See: http://wiki.inspircd.org/Credits + * Copyright (C) 2009 Daniel De Graaf + * Copyright (C) 2008 Craig Edwards * - * This program is free but copyrighted software; see - * the file COPYING for details. + * This file is part of InspIRCd. InspIRCd is free software: you can + * redistribute it and/or modify it under the terms of the GNU General Public + * License as published by the Free Software Foundation, version 2. * - * --------------------------------------------------- + * This program is distributed in the hope that it will be useful, but WITHOUT + * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS + * FOR A PARTICULAR PURPOSE. See the GNU General Public License for more + * details. + * + * You should have received a copy of the GNU General Public License + * along with this program. If not, see . */ -#ifndef __THREADENGINE__ -#define __THREADENGINE__ + +#pragma once #include #include #include -#include "inspircd_config.h" +#include "config.h" #include "base.h" -class InspIRCd; -class Thread; - -/** The ThreadEngine class has the responsibility of initialising - * Thread derived classes. It does this by creating operating system - * level threads which are then associated with the class transparently. - * This allows Thread classes to be derived without needing to know how - * the OS implements threads. You should ensure that any sections of code - * that use threads are threadsafe and do not interact with any other - * parts of the code which are NOT known threadsafe! If you really MUST - * access non-threadsafe code from a Thread, use the Mutex class to wrap - * access to the code carefully. +/** Derive from this class to implement your own threaded sections of + * code. Be sure to keep your code thread-safe and not prone to deadlocks + * and race conditions if you MUST use threading! */ -class CoreExport ThreadEngine : public Extensible +class CoreExport Thread { - protected: - - /** Creator instance - */ - InspIRCd* ServerInstance; - - public: - - /** Constructor. - * @param Instance Creator object + private: + /** Set to true when the thread is to exit */ - ThreadEngine(InspIRCd* Instance); + bool ExitFlag; - /** Destructor + /** Opaque thread state managed by the ThreadEngine */ - virtual ~ThreadEngine(); + ThreadEngine::ThreadState state; - /** Create a new thread. This takes an already allocated - * Thread* pointer and initializes it to use this threading - * engine. On failure, this function may throw a CoreException. - * @param thread_to_init Pointer to a newly allocated Thread - * derived object. + /** ThreadEngine manages Thread::state */ - virtual void Start(Thread* thread_to_init) = 0; + friend class ThreadEngine; - /** Returns the thread engine's name for display purposes - * @return The thread engine name + protected: + /** Get thread's current exit status. + * (are we being asked to exit?) */ - virtual const std::string GetName() + bool GetExitFlag() { - return ""; + return ExitFlag; } -}; - -/** The Mutex class represents a mutex, which can be used to keep threads - * properly synchronised. Use mutexes sparingly, as they are a good source - * of thread deadlocks etc, and should be avoided except where absolutely - * neccessary. Note that the internal behaviour of the mutex varies from OS - * to OS depending on the thread engine, for example in windows a Mutex - * in InspIRCd uses critical sections, as they are faster and simpler to - * manage. - */ -class CoreExport Mutex -{ - protected: - /** Enable or disable the Mutex. This method has somewhat confusing - * wording (e.g. the function name and parameters) so it is protected - * in preference of the Lock() and Unlock() methods which are user- - * accessible. - * - * @param enable True to enable the mutex (enter it) and false to - * disable the mutex (leave it). - */ - virtual void Enable(bool enable) = 0; public: - - /** Constructor. + /** Set Creator to NULL at this point */ - Mutex(); + Thread() : ExitFlag(false) + { + } - /** Enter/enable the mutex lock. + /** Override this method to put your actual + * threaded code here. */ - void Lock() { Enable(true); } + virtual void Run() = 0; - /** Leave/disable the mutex lock. + /** Signal the thread to exit gracefully. */ - void Unlock() { Enable(false); } + virtual void SetExitFlag(); - /** Destructor + /** Join the thread (calls SetExitFlag and waits for exit) */ - ~Mutex() { } + void join(); }; -class CoreExport ThreadData -{ - public: - virtual void FreeThread(Thread* thread) { } -}; -/** Derive from this class to implement your own threaded sections of - * code. Be sure to keep your code thread-safe and not prone to deadlocks - * and race conditions if you MUST use threading! - */ -class CoreExport Thread : public Extensible +class CoreExport QueuedThread : public Thread { - private: - /** Set to true when the thread is to exit + ThreadQueueData queue; + protected: + /** Waits for an enqueue operation to complete + * You MUST hold the queue lock when you call this. + * It will be unlocked while you wait, and will be relocked + * before the function returns */ - bool ExitFlag; + void WaitForQueue() + { + queue.Wait(); + } public: - /** Opaque thread state managed by threading engine + /** Lock queue. */ - ThreadData* state; - - /** Set Creator to NULL at this point + void LockQueue() + { + queue.Lock(); + } + /** Unlock queue. */ - Thread() : ExitFlag(false), state(NULL) + void UnlockQueue() { + queue.Unlock(); } - - /** If this thread has a Creator set, call it to - * free the thread + /** Unlock queue and wake up worker */ - virtual ~Thread() + void UnlockQueueWakeup() { - if (state) - { - state->FreeThread(this); - delete state; - } + queue.Wakeup(); + queue.Unlock(); } + void SetExitFlag() CXX11_OVERRIDE + { + queue.Lock(); + Thread::SetExitFlag(); + queue.Wakeup(); + queue.Unlock(); + } +}; - /** Override this method to put your actual - * threaded code here. +class CoreExport SocketThread : public Thread +{ + ThreadQueueData queue; + ThreadSignalData signal; + protected: + /** Waits for an enqueue operation to complete + * You MUST hold the queue lock when you call this. + * It will be unlocked while you wait, and will be relocked + * before the function returns */ - virtual void Run() = 0; - - /** Signal the thread to exit gracefully. + void WaitForQueue() + { + queue.Wait(); + } + public: + /** Notifies parent by making the SignalFD ready to read + * No requirements on locking */ - void SetExitFlag(bool value) + void NotifyParent(); + SocketThread(); + virtual ~SocketThread(); + /** Lock queue. + */ + void LockQueue() { - ExitFlag = value; + queue.Lock(); } - - /** Get thread's current exit status. - * (are we being asked to exit?) + /** Unlock queue. */ - bool GetExitFlag() + void UnlockQueue() { - return ExitFlag; + queue.Unlock(); + } + /** Unlock queue and send wakeup to worker + */ + void UnlockQueueWakeup() + { + queue.Wakeup(); + queue.Unlock(); + } + void SetExitFlag() CXX11_OVERRIDE + { + queue.Lock(); + Thread::SetExitFlag(); + queue.Wakeup(); + queue.Unlock(); } -}; - - - -#endif + /** + * Called in the context of the parent thread after a notification + * has passed through the socket + */ + virtual void OnNotify() = 0; +};