* is rpc_call blocking and wait for reponse before returning to the caller?
@ 2005-10-27 16:45 Xin Zhao
2005-10-27 17:02 ` Trond Myklebust
0 siblings, 1 reply; 2+ messages in thread
From: Xin Zhao @ 2005-10-27 16:45 UTC (permalink / raw)
To: linux-kernel
I am trying to implement a mechanism similar to rpc. So I might want
to know whether rpc_call return only after it receive response from
the server.
If so, how does it achieve asynchronous operation?
Thanks,
Xin
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: is rpc_call blocking and wait for reponse before returning to the caller?
2005-10-27 16:45 is rpc_call blocking and wait for reponse before returning to the caller? Xin Zhao
@ 2005-10-27 17:02 ` Trond Myklebust
0 siblings, 0 replies; 2+ messages in thread
From: Trond Myklebust @ 2005-10-27 17:02 UTC (permalink / raw)
To: Xin Zhao; +Cc: linux-kernel
to den 27.10.2005 klokka 12:45 (-0400) skreiv Xin Zhao:
> I am trying to implement a mechanism similar to rpc. So I might want
> to know whether rpc_call return only after it receive response from
> the server.
In newer kernels rpc_call is just a wrapper to rpc_call_sync() which is
the synchronous RPC call interface. That will always wait for a response
from the server before returning if the clnt->cl_soft flag is not set.
For asynchronous operation, there is rpc_call_async().
Cheers,
Trond
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-10-27 17:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-10-27 16:45 is rpc_call blocking and wait for reponse before returning to the caller? Xin Zhao
2005-10-27 17:02 ` Trond Myklebust
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®