|
Size: 2941
Comment:
|
Size: 1341
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| SAFplus provides library initialization infrastructure: log, utils, osal, timer... They're the basic libraries that most application should use. However, not all of them would be used. Furthermore, it's necessary to be able to explicitly link individual libs for highly embedded users. |
SAFplus provides library initialization infrastructure: log, utils, osal, timer... They're the basic libraries that most applications should use. However, not all of them would be used. Furthermore, it's necessary to be able to explicitly link individual libraries for highly embedded users. |
| Line 8: | Line 8: |
| The Thread Pool is a client library that is linked with every component that uses it. | SAFplus initialization can be implemented in 2 methods: |
| Line 10: | Line 10: |
| The thread pool contains APIs to add a "Poolable" or "Wakeable" object into an internal job list. When a thread in the pool frees up, it grabs a "Poolable" or "Wakeable" object off the job list and executes it within the thread. | === Method 1: using weak link === According to GNU weak attribute declaration, we can declare initialization functions as the weak linked functions. Therefore, their definitions can be omitted (in case they're not used), or replaced by different libraries (in case they're used). The linker will fill in NULL for undefined weak symbols. |
| Line 12: | Line 13: |
| To preserve resources, if there are many idle threads they will slowly exit down to a configured minimum number. But if the job list exceeds a configured threshold, a new thread will be created up to a configured maximum. == Header == #include <clThreadPool.hxx> |
=== Header === #include <clGlobals.hxx> |
| Line 22: | Line 21: |
| // Definition of user task typedef void (*CallbackT) (void* invocation); typedef uint32_t (*UserCallbackT) (void* invocation); |
extern void utilsInitialize() __attribute__((weak)); extern void logInitialize() __attribute__((weak)); // TODO: other initialization functions declaration here |
| Line 26: | Line 25: |
| class Poolable: public Wakeable | enum |
| Line 28: | Line 27: |
| public: struct timespec m_startTime; struct timespec m_endTime; uint32_t m_executionTimeLimit; bool deleteWhenComplete; /** Flag that indicates this object should be deleted when it is finished running */ Poolable(uint_t timeLimit=30000); /** by default allow a 30 second execution time */ virtual void wake(int amt,void* cookie=NULL); /** Implement this virtual function to do the job */ virtual ~Poolable(); |
RPC=1, CKPT=2, IOC=4, UTILS=8, OSAL=16, LOG=32 |
| Line 39: | Line 35: |
| class ThreadPool { protected: void createTask(); void startNewTask(); void taskEntry(); protected: short m_minThread; short m_maxThread; short m_numIdleTasks; short m_flags; Mutex m_mutex; Wakeable preIdleFn; void* m_preIdleCookie; Wakeable onDeckFn; void* m_onDeckCookie; ThreadCondition m_cond; uint32_t m_pendingJobs; public: ThreadPool(uint_t minThreads, uint_t maxThreads); /* Initialize pool */ /** Starts the thread pool running */ void start(); /** Stops the thread pool. All currently running threads complete their job and then exit */ void stop(); |
void safplusInitialize(uint16_t svc) { if(svc&LOG) if(logInitialize) logInitialize(); if(svc&UTILS) if(utilsInitialize) utilsInitialize(); // TODO: other ones here } |
| Line 67: | Line 44: |
| /** Adds a job into the thread pool. Poolable is NOT COPIED; do not delete or let it fall out of scope. A Poolable object is more sophisticated than a Wakeable; it measures how long it was run for, can track whether it should be deleted, and will ASSERT if it is running for longer than a configured limit (deadlock detector) */ void run(Poolable* p,void* arg); /** Adds a job into the thread pool. Wakeable is NOT COPIED; do not delete or let it fall out of scope */ void run(Wakeable* p,void* arg); ~ThreadPool(); /* Finalize pool */ }; |
SAFplus initialization
SAFplus provides library initialization infrastructure: log, utils, osal, timer... They're the basic libraries that most applications should use. However, not all of them would be used. Furthermore, it's necessary to be able to explicitly link individual libraries for highly embedded users.
Implementation
SAFplus initialization can be implemented in 2 methods:
Method 1: using weak link
According to GNU weak attribute declaration, we can declare initialization functions as the weak linked functions. Therefore, their definitions can be omitted (in case they're not used), or replaced by different libraries (in case they're used). The linker will fill in NULL for undefined weak symbols.
Header
#include <clGlobals.hxx>
APIs
1 namespace SAFplus
2 {
3 extern void utilsInitialize() __attribute__((weak));
4 extern void logInitialize() __attribute__((weak));
5 // TODO: other initialization functions declaration here
6
7 enum
8 {
9 RPC=1,
10 CKPT=2,
11 IOC=4,
12 UTILS=8,
13 OSAL=16,
14 LOG=32
15 };
16
17 void safplusInitialize(uint16_t svc)
18 {
19 if(svc&LOG)
20 if(logInitialize) logInitialize();
21 if(svc&UTILS)
22 if(utilsInitialize) utilsInitialize();
23 // TODO: other ones here
24 }
25
26 }