are all threads exclusive to this pool
the function to execute in the threads of this pool
the user data for the threads of this pool
Frees all resources allocated for pool.
If immediate is %TRUE, no new task is processed for pool.
Otherwise pool is not freed before the last task is processed.
Note however, that no thread of this pool is interrupted while
processing a task. Instead at least all still running threads
can finish their tasks before the pool is freed.
If wait_ is %TRUE, this function does not return before all
tasks to be processed (dependent on immediate, whether all
or only the currently running) are ready.
Otherwise this function returns immediately.
After calling this function pool must not be used anymore.
should pool shut down immediately?
should the function wait for all tasks to be finished?
Returns the maximal number of threads for pool.
Returns the number of threads currently running in pool.
Moves the item to the front of the queue of unprocessed items, so that it will be processed next.
an unprocessed item in the pool
Inserts data into the list of tasks to be executed by pool.
When the number of currently running threads is lower than the
maximal allowed number of threads, a new thread is started (or
reused) with the properties given to g_thread_pool_new().
Otherwise, data stays in the queue until a thread in this pool
finishes its previous task and processes data.
error can be %NULL to ignore errors, or non-%NULL to report
errors. An error can only occur when a new thread couldn't be
created. In that case data is simply appended to the queue of
work to do.
Before version 2.32, this function did not return a success status.
a new task for pool
Sets the maximal allowed number of threads for pool.
A value of -1 means that the maximal number of threads
is unlimited. If pool is an exclusive thread pool, setting
the maximal number of threads to -1 is not allowed.
Setting max_threads to 0 means stopping all work for pool.
It is effectively frozen until max_threads is set to a non-zero
value again.
A thread is never terminated while calling func, as supplied by
g_thread_pool_new(). Instead the maximal number of threads only
has effect for the allocation of new threads in g_thread_pool_push().
A new thread is allocated, whenever the number of currently
running threads in pool is smaller than the maximal number.
error can be %NULL to ignore errors, or non-%NULL to report
errors. An error can only occur when a new thread couldn't be
created.
Before version 2.32, this function did not return a success status.
a new maximal number of threads for pool, or -1 for unlimited
Returns the number of tasks still unprocessed in pool.
This function will return the maximum interval that a
thread will wait in the thread pool for new tasks before
being stopped.
If this function returns 0, threads waiting in the thread pool for new work are not stopped.
Returns the maximal allowed number of unused threads.
Returns the number of currently unused threads.
This function will set the maximum interval that a thread
waiting in the pool for new tasks can be idle for before
being stopped. This function is similar to calling
g_thread_pool_stop_unused_threads() on a regular timeout,
except this is done on a per thread basis.
By setting interval to 0, idle threads will not be stopped.
The default value is 15000 (15 seconds).
the maximum interval (in milliseconds) a thread can be idle
Sets the maximal number of unused threads to max_threads.
If max_threads is -1, no limit is imposed on the number
of unused threads.
The default value is 2.
maximal number of unused threads
Stops all currently unused threads. This does not change the maximal number of unused threads. This function can be used to regularly stop all unused threads e.g. from g_timeout_add().
The #GThreadPool struct represents a thread pool. It has three public read-only members, but the underlying struct is bigger, so you must not copy this struct.