aboutsummaryrefslogtreecommitdiffstats
path: root/src/libstrongswan/processing
Commit message (Collapse)AuthorAgeFilesLines
* lib: All settings use configured namespaceTobias Brunner2014-02-121-1/+1
|
* watcher: Don't complain if select() syscall got interruptedMartin Willi2014-01-221-1/+1
|
* watcher: Rebuild fdset when select() failsMartin Willi2013-10-241-1/+12
| | | | | | This should make sure we refresh the fdset if a user closes an FD it just removed. Some selects() seem to complain about the bad FD before signaling the notification pipe.
* watcher: Made notify array initialization compatible with older GCC versionsTobias Brunner2013-07-251-2/+1
|
* processor: force synchronous execute_job() if set_threads(0) has been calledMartin Willi2013-07-191-1/+1
| | | | | | During daemon shutdown, some idle threads might be lingering around even if set_threads(0) already has been called. To avoid any races, we enforce synchronous execution of the job.
* Fix various API doc issues and typosTobias Brunner2013-07-181-1/+1
| | | | Partially based on an old patch by Adrian-Ken Rueegsegger.
* processor: remove the now unused get_threads() method againMartin Willi2013-07-182-17/+0
|
* watcher: use processors new execute_job() to notify FDsMartin Willi2013-07-181-9/+1
| | | | | Just queueing is problematic, as all threads might be busy waiting for events that the queued (but never executed) job delivers.
* processor: add an execute_job() method to directly execute an important jobMartin Willi2013-07-182-0/+36
| | | | | | | If all worker threads are busy and waiting for an event, we must ensure that a job delivering that event gets executed. This new method has this property for CRITICAL jobs, using a worker if we have one, but executing the job directly if not.
* watcher: properly support multiple watch callback types for the same FDMartin Willi2013-07-182-36/+45
|
* watcher: read multiple notifications if availableMartin Willi2013-07-181-2/+15
| | | | | Use non-blocking I/O on the read end of the notify pipe. This also makes sure the read does not block should select() signal data while there is none.
* watcher: add some debugging statementsMartin Willi2013-07-181-0/+12
|
* watcher: if the processor has no threads, execute the job with watcher threadMartin Willi2013-07-181-11/+19
| | | | | This is important during shutdown, where we might need to signal some FDs while all idle threads are gone already.
* processor: add a getter for the threads passed to set_threads()Martin Willi2013-07-182-1/+17
|
* watcher: unregister a watcher FD if its thread gets cancelledMartin Willi2013-07-181-0/+13
|
* watcher: release threads waiting in remove() when watcher thread gets cancelledMartin Willi2013-07-181-0/+24
| | | | | | | During daemon shutdown, users might call remove() after processor.set_threads(0) has been called. This gets problematic, as a watch event might be unable to signal completion when no threads are available anymore. Work around this issue by cancelling waiters once processor.cancel() has been called.
* watcher: add a centralized an generic facility to monitor file descriptorsMartin Willi2013-07-182-0/+493
|
* processor: Simplified the main loopTobias Brunner2013-06-281-109/+127
|
* processor: Don't hold the lock while destroying jobsTobias Brunner2013-06-281-38/+66
| | | | | | If a lock is held when queue_job() is called and the same lock is required during the destruction of a job, holding the internal lock in the processor while calling destroy() could result in a deadlock.
* Moved debug.[ch] to utils folderTobias Brunner2012-10-242-2/+2
|
* Moved data structures to new collections subfolderTobias Brunner2012-10-242-2/+2
|
* Make rescheduling a job more predictableTobias Brunner2012-06-252-37/+85
| | | | | | | | | | | | | This avoids race conditions between calls to cancel() and jobs that like to be rescheduled. If jobs were able to reschedule themselves it would theoretically be possible that two worker threads have the same job assigned (the one currently executing the job and the one executing the same but rescheduled job if it already is time to execute it), this means that cancel() could be called twice for that job. Creating a new job based on the current one and reschedule that is also OK, but rescheduling itself is more efficient for jobs that need to be executed often.
* Centralized thread cancellation in processor_tTobias Brunner2012-06-256-206/+124
| | | | | | | | | | This ensures that no threads are active when plugins and the rest of the daemon are unloaded. callback_job_t was simplified a lot in the process as its main functionality is now contained in processor_t. The parent-child relationships were abandoned as these were only needed to simplify job cancellation.
* Give processor_t more control over the lifecycle of a jobTobias Brunner2012-06-256-105/+176
| | | | | | | | | | | Jobs are now destroyed by the processor, but they are allowed to reschedule themselves. That is, parts of the reschedule functionality already provided by callback_job_t is moved to the processor. Not yet fully supported is JOB_REQUEUE_DIRECT and canceling jobs. Note: job_t.destroy() is now called not only for queued jobs but also after execution or cancellation of jobs. job_t.status can be used to decide what to do in said method.
* Use wrapped semaphore in callback_job_t.Tobias Brunner2012-05-021-12/+9
|
* Log worker thread ID with two digits.Tobias Brunner2011-12-161-2/+2
|
* Fixed compiler warnings regarding enum comparison.Tobias Brunner2011-11-251-1/+1
| | | | | | | | | Warnings like comparison of unsigned expression < 0 is always false are reported with -Wextra when enum types that are compiled to an unsigned type (which is up to the compiler) are checked for negativity.
* Fixed common misspellings.Tobias Brunner2011-07-202-2/+2
| | | | Mostly found by 'codespell'.
* Prevent deadlock while shutting down thread pool.Tobias Brunner2011-06-081-2/+2
| | | | | | | | | During destruction the main thread locks the mutex in processor_t and waits on a condvar for threads to have terminated. Because the mutex has also to be locked to decrement the thread count the condvar cannot be signaled before doing that as otherwise the main thread might already be waiting to join the threads while locking the mutex and thus causing a deadlock.
* Update working thread count without allocation.Tobias Brunner2011-05-161-22/+15
|
* Make sure working thread count is correctly updatedTobias Brunner2011-05-161-4/+23
|
* Use CRITICAL job priority class for long running dispatcher jobsMartin Willi2011-05-161-1/+2
|
* Introduce a highest priority job for critical thread servicesMartin Willi2011-05-162-2/+5
|
* Added a callback_job constructor supporting custom prioritiesMartin Willi2011-05-162-4/+36
|
* Count number of threads active in each class, and reserve threads only if ↵Martin Willi2011-05-162-17/+66
| | | | none active
* Reserve threads for job priority classes based on strongswan.conf optionsMartin Willi2011-05-161-1/+17
|
* Added job priority enum namesMartin Willi2011-05-162-0/+27
|
* Processor job scheduling respects job priority classesMartin Willi2011-05-162-13/+47
|
* Introduce priority classes for jobsMartin Willi2011-05-162-2/+30
|
* Migrated scheduler_t to INIT/METHOD macrosMartin Willi2011-05-051-33/+24
|
* Migrated callback_job to INIT/METHOD macrosMartin Willi2011-05-052-38/+38
|
* Migrated processor to INIT/METHOD macrosMartin Willi2011-05-051-42/+35
|
* Do not invoke processor restart() if not requiredMartin Willi2011-03-151-1/+2
| | | | | Doing so might result in a deadlock during shutdown if a delayed restart is locked on the bus during the debug statement.
* Remove obsolete pool_size argument in processor_create()Martin Willi2010-11-161-1/+1
|
* Refer to scheduler and processor via lib and not hydra.Tobias Brunner2010-09-022-6/+4
|
* Moved scheduler and thread pool to libstrongswan.Tobias Brunner2010-09-027-0/+1298
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-31 01:31:28 +0000