> >> I think merging the rumpfiber, xen and baremetal implementations is > >> probably a good start - will take a look at it. Basically will look at > >> adding the assembly implementation of stack switching as an option, > >> which is the main difference. > > > > Merging _lwp.c? Where are you going to host the unified implementation? > > well its not mainly about merging _lwp.c, it is merging some of the > rumpuser implementations... ideally to be hosted in netbsd but will > see. Needs some thought.
Which parts of the rumprun-* stacks are currently shared (or at least descended from common code), aside from the NetBSD rump kernel obviously? I understand there's a NetBSD libc in there but it's not clear to me if this is specifically modified for each stack and if so, how? In the long run, which parts (of rumprun-*) would you like to see further sharing code? > m-n threading is a pain, best avoided, if you want parallelism just > use some sort of native thread exclusively. Plus there are some good > reasons to avoid pthreads that I am working on. +1 for avoiding m-n threading. What are your reasons for avoiding pthreads? Martin ------------------------------------------------------------------------------ _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
