Hi,
With this patch there is a rpc_clnt for each client options set (softrtry,
chatty, intr). These clients are associated with a host. They are destroyed
when performing nlm_gc_hosts.
The client, once allocated is kept in the nlm_rqst structure, thus the client
may call nlm_bind_host with the reference on the allready allocated rpc_clnt
with the right rpc call options (in nlmclnt_async_call, nlmclnt_call).
On the server side, nlm_bind_host is called with a NULL rpc_clnt, and this
trigger nlm_bind_host to use h_rpcclnt as a client.
On the client side, there are 2 situation in which the h_rpcclnt is used,
with default options:
* when there is a cancel call
In that case, the nlm_rqst isn't used, a new one is allocated instead. Is
it a correct behavior ?
Even if it is the correct behavior, it should be quite easy to get a
client with the right options.
* when the client responds to a granted_msg call, as it uses nlmsvc_callback.
Should it be fixed ?
Pat