From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Xin Zhao <uszhaoxin@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: is rpc_call blocking and wait for reponse before returning to the caller?
Date: Thu, 27 Oct 2005 13:02:24 -0400 [thread overview]
Message-ID: <1130432544.21372.35.camel@lade.trondhjem.org> (raw)
In-Reply-To: <4ae3c140510270945w286cbcf5j7e7a4bde454526b5@mail.gmail.com>
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
prev parent reply other threads:[~2005-10-27 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 16:45 Xin Zhao
2005-10-27 17:02 ` Trond Myklebust [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1130432544.21372.35.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=uszhaoxin@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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®