About TODO Blog RSS Old blog Projects Gallery Notes

Sun, 04 Mar 2007

Kevent.


In case you were confused about this post that I never used any project to advertise kevent and this post about how I used threadlet thread to advertise kevent.
The latter is a very ironic post about the only possibility to get attention is only by entering some other thread (remotely related) and start agressively stating own point of view. If you think otherwise - that is your problems and basicvally you suck.
I indeed did that, but that was not done to show that threadlets suck and kevent is cool.
Absolutely.
I like Ingo's approach of threadlets and agree that it is a very simple and quite non-problematic case to create highly parallized environment, but I just think (based on my expirience with threads in Linux) that threads per IO (or per block) is not a good solution for AIO model. I do not say, that it is worse than kevent (or any other event-driven model), I just want to say, that as is it is not the best solution from performance point of view, and both event driven (kevent or epoll, the former will be declined almost sure, I proposed another idea - having new filesystem for each type of events, i.e. signalfs, timerfs and so one, that approach does have problems and scales worse than kevent (it is bound to file structure, which is quite heavy), but it allows to have epoll as a controlling interface) model.
Although it does requre to write new code both in kernelspace and userspace, and to change existing applications just like kevent, and likely scales worse than kevent, which is there already, it probably will be blessed by developers.
But I do not care actually :)
There are a lot of other interesting things (without politics).
Stay tuned.

/devel/kevent :: Link / Comments (0)

Comments are closed for this story.