| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
this is a perquisite for multi-threading the input handler
|
| |
|
|
|
|
| |
so far, we always pulled a single event from the epoll interface.
Now 128, what should result in performance improvement (less API
calls) on busy systems. Most importantly affects imtcp.
|
| |
|
|
|
|
|
|
| |
by implementing some code that was missing so far ;) as well as
finding some real bugs. I also did some general cleanup, removing
debug strings and such. This code should be fairly OK to use, except
when "exec only when previous action was suspended" is used -- this is
NOT yet re-implemented in the tuned engine.
|
| |
|
|
| |
... but not well-tested, so there may be many hidden bugs.
|
| |
|
|
| |
NOTE: this version does NOT run - tcp-based servers are defunct.
|
| |
|
|
|
| |
... does not really run. We can now call into the epoll driver, but
not handle epoll(). The driver also needs more modifications.
|
| |
|
