On 25/02/14 16:19, Martin Unzner wrote: > On a slightly related topic: You said the semantics for host signals > vary. For example, does a SIGALRM from the host interrupt a Rump accept > syscall? Thanks a lot! Martin
Currently, a signal will never interrupt any rump kernel syscall. Note that while there is a concept for signal delivery inside the rump kernel (because kernel drivers depend on it), the signal will always be delivered by the host. So the following do more or less the same when run in userspace: setitimer(...) rump_sys_accept(...) and: rump_sys_setitimer(...) rump_sys_accept(...) (except that rump_sys_setitimer() is not in the public tree, as I'm still mulling over what to do with it, but YKWIM) That said, why go looking for synchronization problems and race conditions with signals when you could just as easily use poll()? ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
