RPC Vs Simple Procedure Call - Georgia Tech - Advanced Operating Systems

[svarodzic]

Dude, nothing happens at compile time except compiling. SPC also happens at runtime! Probably what you really meant to state as differences are: the same process vs different processes, synchronous (blocking call) vs asynchronous (none-blocking) (in the first approximation). As for compile time, you probably meant function binding - static binding at compile time vs dynamic binding at runtime. But +1 anyway, cuz it's a good explanation!

[MultiWiff]

I think there's a confusion from the video is that in SPC the caller locates the callee at compile time by literally copying the memory address of callee's instruction into the instruction register. Meanwhile, in RPC, the caller and callee are on a separate machine where there is no shared memory address space therefore caller cannot pinpoint the callee at compile-time and rely on runtime check.

[chenyang_wu]

What are the call trap and return trap?

[govamurali]

can you please tell where the kernel resides at?

[sathyajithhv]

Great now i gotta google half of the keywords he said in the video !

[macbook_]

what does "procedure call happens in compile time" exactly mean? At compile time, the program is not running, there is no process established for the program, how can the call happen? This part is very ambiguous and not convincing, please clarify.

[FertassiFarah]

I really like short videos. But that would have been good to talk about RPC in case of distributed system. From the other videos on video, I understand what you explained is Lightweight RPC. Am I correct?

[jimgeoshuabactad]

Aint it supposed to be " At runtime"?

[WissalBe]

Too basic, you should have detailed more or made it way shorter than 5min.

[hello]

I don't think this is correct explanation. What do you mean local procedure call happens in compile time? Both LPC and RPC happens in run time. It's just matter of what do LPC and RPC do in compile time and run time are different.