[lkml]   [2003]   [Feb]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Remote execution of syscalls (was Re: Syscall from Kernel Space)
Followup to:  <>
By author: Prasad <>
In newsgroup:
> 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.

<> at work, <> 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
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:33    [W:0.055 / U:1.548 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site