On Jun 11, 2009, at 12:49 AM, Neil Brown wrote:
On Thursday May 28, tmtalpey@xxxxxxxxx wrote:
At 02:33 AM 5/28/2009, NeilBrown wrote:
Unregistering an RPC service is not essential - but it is tidy.
So it is unpleasant to wait a long time for it to complete.
As unregistering is always directed to localhost, the most likely
reason for any delay is the portmap (or rpcbind) is not running.
In that case, waiting it totally pointless. In any case, we should
expect a quick response, and zero packet loss.
So reduce the timeouts to a total of half a second.
Why wait for the response at all in this case? With zero retries
and nothing to do with the result, it seems pointless to even wait
for half a second.
That's a fair point, thanks. I'll keep that in mind if I revisit
these patches.
While not waiting is probably OK in the "shutdown" case, it could be a
problem during normal operation. The kernel unregisters RPC services
before it attempts to register them (to clear any old registrations).
Not waiting for the unregister reply might be racy.
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
