Hello Tobias,
Additionally I will have to cope with the question how to distinguish between ipc calls which are aactual request and ipc calls which are replies to a previously send call (for asynchronous send calls).
Maybe I am missing something, but can you simply make use of the fact that the requests and replies are first-class entities in HelenOS IPC? Every request needs a reply, otherwise the kernel will keep the original request in its data structures and the total size of the list of unanswered requests is bounded.
BTW: As the mapping between the SPARTAN and Genode IPC concepts and the relation between the two implementations are becoming more and more complex, it might be helpful if you start documenting it. A simple wiki page (perhaps on http://trac.helenos.org/) might do. I was thinking about a table or set of tables with the Genode concepts/classes/terms/code snippets on one side and the SPARTAN concepts/types/terms/code snippets which they are mapped to on the other side.
I know that a good code is self-documenting :), but it would be bad if the relation between the two worlds would stay only in your head. Documenting it should also help us help you more effectively.
M.D. _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
