mirrors/kore
1
0
Fork 1
mirror of https://git.kore.io/kore.git synced 2024-11-11 12:49:32 +01:00
Code Issues Projects Releases Wiki Activity
a5342a0120
kore/include/kore/tasks.h

99 lines
2.5 KiB
C
Raw Normal View History

Add initial stab at asynchronous background tasks. More to follow.
2014-06-28 16:17:18 +02:00
/*
* Copyright (c) 2014 Joris Vink <joris@coders.se>
*
* Permission to use, copy, modify, and distribute this software for any
* purpose with or without fee is hereby granted, provided that the above
* copyright notice and this permission notice appear in all copies.
*
* THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
* WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
* MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
* ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
* WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
* ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
* OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
*/
#ifndef __H_KORE_TASKS
#define __H_KORE_TASKS
Include pthread.h in tasks.h, fixes compilation under OpenBSD
2014-07-18 15:51:13 +02:00
#include <pthread.h>
Move tasks away from http_requests. Instead if a task is used from inside a request you MUST call kore_task_bind_request() on it. This way we can move forward for tasks that don't belong to page handlers. Also, some bug fixes for removing http_requests that are indeed linked to a currently running task.
2014-06-29 20:20:13 +02:00
#define KORE_TASK_STATE_CREATED 1
#define KORE_TASK_STATE_RUNNING 2
#define KORE_TASK_STATE_FINISHED 3
Task improvements. Synchronize access to state/result properly so one can access these from inside the task as well. Introduce KORE_TASK_STATE_ABORT which will be set when a task needs to be abort. You can use this to create tasks that run in a loop until aborted.
2014-07-04 11:28:17 +02:00
#define KORE_TASK_STATE_ABORT 4
Move tasks away from http_requests. Instead if a task is used from inside a request you MUST call kore_task_bind_request() on it. This way we can move forward for tasks that don't belong to page handlers. Also, some bug fixes for removing http_requests that are indeed linked to a currently running task.
2014-06-29 20:20:13 +02:00
Add task_threads configuration option. Before Kore would spawn a task thread per task started if none were available. This was an obvious bad idiom but never really hit me hard until now. Kore will now only spawn as many task threads as configured by "task_threads" and queue up any newly started tasks ontop of already running threads if the limit was hit.
2015-06-04 10:29:22 +02:00
#define KORE_TASK_THREADS 2
Add __cplusplus macros to headers.
2015-04-01 13:25:10 +02:00
#if defined(__cplusplus)
extern "C" {
#endif
Introduce NOHTTP=1 build option. This basically turns off the HTTP layer for Kore. It does not compile in anything for HTTP. This allows Kore to be used as a network application platform as well. Added an example for this called nohttp. Other changes that sneaked in while hacking on this: * Use calloc(), kill pendantic malloc option. * Killed off SPDY/3.1 support completely, will be superseded by http2 Note that comes with massive changes to a lot of the core API functions provided by Kore, these might break your application.
2015-11-27 16:22:50 +01:00
#if !defined(KORE_NO_HTTP)
Move tasks away from http_requests. Instead if a task is used from inside a request you MUST call kore_task_bind_request() on it. This way we can move forward for tasks that don't belong to page handlers. Also, some bug fixes for removing http_requests that are indeed linked to a currently running task.
2014-06-29 20:20:13 +02:00
struct http_request;
Introduce NOHTTP=1 build option. This basically turns off the HTTP layer for Kore. It does not compile in anything for HTTP. This allows Kore to be used as a network application platform as well. Added an example for this called nohttp. Other changes that sneaked in while hacking on this: * Use calloc(), kill pendantic malloc option. * Killed off SPDY/3.1 support completely, will be superseded by http2 Note that comes with massive changes to a lot of the core API functions provided by Kore, these might break your application.
2015-11-27 16:22:50 +01:00
#endif
Move tasks away from http_requests. Instead if a task is used from inside a request you MUST call kore_task_bind_request() on it. This way we can move forward for tasks that don't belong to page handlers. Also, some bug fixes for removing http_requests that are indeed linked to a currently running task.
2014-06-29 20:20:13 +02:00
Add initial stab at asynchronous background tasks. More to follow.
2014-06-28 16:17:18 +02:00
struct kore_task {
Changes to the event loop inside of Kore. Now anyone can schedule events and get a callback to work as long as the user data structure that is added for the event begins with a kore_event data structure. All event state is now kept in that kore_event structure and renamed CONN_[READ|WRITE]_POSSIBLE to KORE_EVENT_[READ|WRITE].
2018-10-09 19:34:40 +02:00
struct kore_event evt;
Task improvements. Synchronize access to state/result properly so one can access these from inside the task as well. Introduce KORE_TASK_STATE_ABORT which will be set when a task needs to be abort. You can use this to create tasks that run in a loop until aborted.
2014-07-04 11:28:17 +02:00
int state;
int result;
pthread_rwlock_t lock;
Move tasks away from http_requests. Instead if a task is used from inside a request you MUST call kore_task_bind_request() on it. This way we can move forward for tasks that don't belong to page handlers. Also, some bug fixes for removing http_requests that are indeed linked to a currently running task.
2014-06-29 20:20:13 +02:00
Introduce NOHTTP=1 build option. This basically turns off the HTTP layer for Kore. It does not compile in anything for HTTP. This allows Kore to be used as a network application platform as well. Added an example for this called nohttp. Other changes that sneaked in while hacking on this: * Use calloc(), kill pendantic malloc option. * Killed off SPDY/3.1 support completely, will be superseded by http2 Note that comes with massive changes to a lot of the core API functions provided by Kore, these might break your application.
2015-11-27 16:22:50 +01:00
#if !defined(KORE_NO_HTTP)
Move tasks away from http_requests. Instead if a task is used from inside a request you MUST call kore_task_bind_request() on it. This way we can move forward for tasks that don't belong to page handlers. Also, some bug fixes for removing http_requests that are indeed linked to a currently running task.
2014-06-29 20:20:13 +02:00
struct http_request *req;
Introduce NOHTTP=1 build option. This basically turns off the HTTP layer for Kore. It does not compile in anything for HTTP. This allows Kore to be used as a network application platform as well. Added an example for this called nohttp. Other changes that sneaked in while hacking on this: * Use calloc(), kill pendantic malloc option. * Killed off SPDY/3.1 support completely, will be superseded by http2 Note that comes with massive changes to a lot of the core API functions provided by Kore, these might break your application.
2015-11-27 16:22:50 +01:00
#endif
Move tasks away from http_requests. Instead if a task is used from inside a request you MUST call kore_task_bind_request() on it. This way we can move forward for tasks that don't belong to page handlers. Also, some bug fixes for removing http_requests that are indeed linked to a currently running task.
2014-06-29 20:20:13 +02:00
int fds[2];
Sprinkle volatile
2014-06-30 14:23:04 +02:00
int (*entry)(struct kore_task *);
Add the actual task changes for last commit.
2015-07-01 11:03:54 +02:00
void (*cb)(struct kore_task *);
Add initial stab at asynchronous background tasks. More to follow.
2014-06-28 16:17:18 +02:00
More work on the background task implementation. Tasks are now assigned to available threads instead of a global task list. You can now pass messages between your page handler and the created task using the kore_task_channel_* functions. Only one task per time can be assigned to a request but I feel this is probably a bad design choice. Preferably we'd want to be able to start tasks regardless of being in a page handler or not, this not only ads flexibility but seems like a better choice overall as it opens a lot more possibilities about how tasks can be used.
2014-06-29 14:15:40 +02:00
struct kore_task_thread *thread;
Attach tasks/pgsqls to http_requests once more. This way if an http request is removed while tasks or pgsqls are still active they are free'd out and cancelled properly.
2014-08-14 22:05:34 +02:00
More work on the background task implementation. Tasks are now assigned to available threads instead of a global task list. You can now pass messages between your page handler and the created task using the kore_task_channel_* functions. Only one task per time can be assigned to a request but I feel this is probably a bad design choice. Preferably we'd want to be able to start tasks regardless of being in a page handler or not, this not only ads flexibility but seems like a better choice overall as it opens a lot more possibilities about how tasks can be used.
2014-06-29 14:15:40 +02:00
TAILQ_ENTRY(kore_task) list;
Attach tasks/pgsqls to http_requests once more. This way if an http request is removed while tasks or pgsqls are still active they are free'd out and cancelled properly.
2014-08-14 22:05:34 +02:00
LIST_ENTRY(kore_task) rlist;
Add initial stab at asynchronous background tasks. More to follow.
2014-06-28 16:17:18 +02:00
};
struct kore_task_thread {
More work on the background task implementation. Tasks are now assigned to available threads instead of a global task list. You can now pass messages between your page handler and the created task using the kore_task_channel_* functions. Only one task per time can be assigned to a request but I feel this is probably a bad design choice. Preferably we'd want to be able to start tasks regardless of being in a page handler or not, this not only ads flexibility but seems like a better choice overall as it opens a lot more possibilities about how tasks can be used.
2014-06-29 14:15:40 +02:00
u_int8_t idx;
pthread_t tid;
pthread_mutex_t lock;
pthread_cond_t cond;
TAILQ_HEAD(, kore_task) tasks;
Add initial stab at asynchronous background tasks. More to follow.
2014-06-28 16:17:18 +02:00
TAILQ_ENTRY(kore_task_thread) list;
};
void kore_task_init(void);
Changes to the event loop inside of Kore. Now anyone can schedule events and get a callback to work as long as the user data structure that is added for the event begins with a kore_event data structure. All event state is now kept in that kore_event structure and renamed CONN_[READ|WRITE]_POSSIBLE to KORE_EVENT_[READ|WRITE].
2018-10-09 19:34:40 +02:00
void kore_task_handle(void *, int);
Let tasks only start after kore_task_run() is called.
2014-06-30 14:35:32 +02:00
void kore_task_run(struct kore_task *);
Add initial stab at asynchronous background tasks. More to follow.
2014-06-28 16:17:18 +02:00
void kore_task_finish(struct kore_task *);
void kore_task_destroy(struct kore_task *);
Move tasks away from http_requests. Instead if a task is used from inside a request you MUST call kore_task_bind_request() on it. This way we can move forward for tasks that don't belong to page handlers. Also, some bug fixes for removing http_requests that are indeed linked to a currently running task.
2014-06-29 20:20:13 +02:00
int kore_task_finished(struct kore_task *);
Introduce NOHTTP=1 build option. This basically turns off the HTTP layer for Kore. It does not compile in anything for HTTP. This allows Kore to be used as a network application platform as well. Added an example for this called nohttp. Other changes that sneaked in while hacking on this: * Use calloc(), kill pendantic malloc option. * Killed off SPDY/3.1 support completely, will be superseded by http2 Note that comes with massive changes to a lot of the core API functions provided by Kore, these might break your application.
2015-11-27 16:22:50 +01:00
#if !defined(KORE_NO_HTTP)
Move tasks away from http_requests. Instead if a task is used from inside a request you MUST call kore_task_bind_request() on it. This way we can move forward for tasks that don't belong to page handlers. Also, some bug fixes for removing http_requests that are indeed linked to a currently running task.
2014-06-29 20:20:13 +02:00
void kore_task_bind_request(struct kore_task *,
struct http_request *);
Introduce NOHTTP=1 build option. This basically turns off the HTTP layer for Kore. It does not compile in anything for HTTP. This allows Kore to be used as a network application platform as well. Added an example for this called nohttp. Other changes that sneaked in while hacking on this: * Use calloc(), kill pendantic malloc option. * Killed off SPDY/3.1 support completely, will be superseded by http2 Note that comes with massive changes to a lot of the core API functions provided by Kore, these might break your application.
2015-11-27 16:22:50 +01:00
#endif
Add the actual task changes for last commit.
2015-07-01 11:03:54 +02:00
void kore_task_bind_callback(struct kore_task *,
void (*cb)(struct kore_task *));
Attach tasks/pgsqls to http_requests once more. This way if an http request is removed while tasks or pgsqls are still active they are free'd out and cancelled properly.
2014-08-14 22:05:34 +02:00
void kore_task_create(struct kore_task *,
Sprinkle volatile
2014-06-30 14:23:04 +02:00
int (*entry)(struct kore_task *));
Add initial stab at asynchronous background tasks. More to follow.
2014-06-28 16:17:18 +02:00
More work on the background task implementation. Tasks are now assigned to available threads instead of a global task list. You can now pass messages between your page handler and the created task using the kore_task_channel_* functions. Only one task per time can be assigned to a request but I feel this is probably a bad design choice. Preferably we'd want to be able to start tasks regardless of being in a page handler or not, this not only ads flexibility but seems like a better choice overall as it opens a lot more possibilities about how tasks can be used.
2014-06-29 14:15:40 +02:00
u_int32_t kore_task_channel_read(struct kore_task *, void *, u_int32_t);
Add initial stab at asynchronous background tasks. More to follow.
2014-06-28 16:17:18 +02:00
void kore_task_channel_write(struct kore_task *, void *, u_int32_t);
Task improvements. Synchronize access to state/result properly so one can access these from inside the task as well. Introduce KORE_TASK_STATE_ABORT which will be set when a task needs to be abort. You can use this to create tasks that run in a loop until aborted.
2014-07-04 11:28:17 +02:00
void kore_task_set_state(struct kore_task *, int);
void kore_task_set_result(struct kore_task *, int);
int kore_task_state(struct kore_task *);
int kore_task_result(struct kore_task *);
Add task_threads configuration option. Before Kore would spawn a task thread per task started if none were available. This was an obvious bad idiom but never really hit me hard until now. Kore will now only spawn as many task threads as configured by "task_threads" and queue up any newly started tasks ontop of already running threads if the limit was hit.
2015-06-04 10:29:22 +02:00
extern u_int16_t kore_task_threads;
Add __cplusplus macros to headers.
2015-04-01 13:25:10 +02:00
#if defined(__cplusplus)
}
#endif
Task improvements. Synchronize access to state/result properly so one can access these from inside the task as well. Introduce KORE_TASK_STATE_ABORT which will be set when a task needs to be abort. You can use this to create tasks that run in a loop until aborted.
2014-07-04 11:28:17 +02:00
Add initial stab at asynchronous background tasks. More to follow.
2014-06-28 16:17:18 +02:00
#endif
Reference in New Issue Copy Permalink