Jakub wrote: > The internal resources such as stack will be cleaned up by whatever > fibril is scheduled next. See the 'clean_after_me' fibril member. > fibril_join()/fibril_detach() has not been needed so far, so these will > have to be implemented. Shouldn't be a big deal though. Okay, so that means when I create a fibril now, it is created as detached, i.e. when it terminates, all its resources are automatically freed, right? That should be mostly sufficient.
Another idea, when i create a fibril with fibril_create(), the only way to free its resources is to do fibril_add_ready() and let it run until completion, right? No way to undo fibril_create() with something like fibril_destroy() (if the fibril hasn't been runnable). Just asking, though, this is probably not a big deal. I know it might sound like I am trying to do something awkward and yes, the code will probably be a little non-straightforward. Later I will completely redesign the socket code, which should hopefully simplify things. -Jiri _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
