On 22/06/14 17:26, Justin Cormack wrote: > I added a -F CURLWP=... option, as buildrump.sh was autodetecting that > it should use __thread, but I am writing a hypercall layer that > doesn't use threads so that wasn't that helpful. > > I have left the default at auto, which detects as before, not sure if > that is the best option. Also not entirely sure how the xen hypervisor > has been working.
Xen has been working by specifying -V RUMP_CURLWP=hypercall. I think it would work for you too. Generally speaking, it's probably not worthwhile to maintain two overlapping options both in the NetBSD makefiles and buildrump.sh. ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
