On 11/1/17 2:27 PM, William Allen Simpson wrote:
On 11/1/17 10:07 AM, Frank Filz wrote:
So part of why that code looks bizarre? Because the NLM ASYNC RPC procedures
are bizarre...
The NLM ASYNC procedures DON'T have a normal RPC call response. Instead, the
host handling the call (normally the server, but the client in the case of
NLM_GRANTED for lock grant callbacks) makes an RPC CALL back to the sender!
The RPC library, at least at the time of writing this, had no mechanism to
fire off RPC calls and not care about a response...
Good to know. A feature I can add!
Actually, I can do that right away. My new code splits the call_req
setup from the CLNT_CALL in preparation for true async callbacks.
With this interface exposed, setting cc_refreshes to 0 (default 2)
means it won't try again.
It will still wait, though.
[...]
In a week or two, I'll add the feature to not await a response at all.
And that should also be easy. Will check for NULL callback function.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
