Messages in this thread | | | From | "H. Peter Anvin" <> | Subject | Re: Remote execution of syscalls (was Re: Syscall from Kernel Space) | Date | 24 Feb 2003 17:34:21 -0800 |
| |
Followup to: <Pine.LNX.4.44.0302212321530.6139-100000@students.iiit.net> By author: Prasad <prasad_s@students.iiit.net> In newsgroup: linux.dev.kernel > > > before anything else, thanx for the response, i was very much discouraged > by the fact that i did not get any replies... > > coming to whats happening... lets see it this way... Theres a process (x) > that is migrated to some other node. Now any syscall that the process (X) > makes is to be shipped back to the originating node. Say i have a user > thread (Y) running and receiving requests for syscall executions. And now > if i execute a syscall, the syscall will be executed as of (Y) is > executing it, but i want the syscall to run as if (X) is executing it! > The process (X) still exists on the originating system, but is idle. >
Sounds like you should let the otherwise-idle process X be the thread that waits for the connection and issues system calls. This is basically RPC.
-hpa -- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." Architectures needed: cris ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |