|
Hi Eddie and all, thanks for doing and sharing this great job that is Click. If it's not too late, I would like to suggest some possible and valuable (I hope .-) improvements to Click; some of them, probably, have been already discussed then it'll be one additional vote for these. 1) the multi-threading support in user-level Click for performance reasons. I think that even in user-space, Click could be very very efficient with multiple threads; certainly for SMP machines using Intel Core Duo for instance but also for single CPU machines (where threads are blocked on multiple I/O devices and where poll()/select() may be clearly used less or event not at all). My impression is that, because it works already with the kernel version (and things like spin-locks) it should be achievable. 2) the run-time reconfiguration capability of Click to get a better flexibility in creating/removing new elements and connections. The use case is the following: a new data flow enter the Click process and I would like to create a new socket element that would be used as a proxy for some other running processes; In addition to the creation of this new element, I need then to add a connection between the new element and one other element. This case may happen more than once but I don't know in advance how many times. The point is that I would like to create at run-time new elements and connections to these elements without using the hot-swap feature which is nice but a little bit too heavy for my need; because it swaps all the current elements and connections. Then, I know you have already add_element() and add_connection() in Router class but it's only possible to use them when the router is in ROUTER_NEW state, then definitely not when all the stuff is really processing packets at run-time. Btw it would be nice to have also remove_element() and remove_connection(). 3) related to the previous one, the dynamic loading capability of new element at run-time. This dynamic loading capability (already present through the usage of requirement statements) would be useful when a new element is instantiated because the binary object that contains this element has not been linked yet with the Click process. that's all folks. Best regards, Stéphane. Stéphane Ménoret Software Architect Collaboration Technologies Laboratory (LINC) THALES Research & Technology France Eddie Kohler a écrit : Hi all, I am preparing for a 1.6.0 "stable" Click release. The anonymous CVS has been updated with a NEWS file describing my take on the changes since 1.5.0. In the coming days I will attempt to go through enqueued Click mailing list mail and fix what I can. Please, if you really want something fixed, or you have any complaints, now is the time to send them.A linked list template (one of the things I wanted to include) will not make it into this release. Sorry Jason. Eddie _______________________________________________ click mailing list [email protected] https://amsterdam.lcs.mit.edu/mailman/listinfo/click |
_______________________________________________ click mailing list [email protected] https://amsterdam.lcs.mit.edu/mailman/listinfo/click
