NFS Performance Tuning for HP-UX 11.0 and 11i Systems

nfs performance tuning for hp-ux 11.0 and 11i systems page 61
Notes:
Page 61July 22, 2002
Copyright 2002 Hewlett- Packard Company
rpc.lockd
&
rpc.statd
How are NFS file lock requests
handled by lockd and statd?
text text
CLIENT
2
3 4
15
1 16
SERVER
11
8 9
10
14 7
6
512
13
rpc.statd
rpc.lockd
kernel
application
rpcbind
rpc.statd
rpc.lockd
kernel
application
rpcbind
1. Application on the client requests to lock a file – the request goes to the kernel
2. Kernel resolves pathname to NFS rnode – forwards request to local rpc.lockd
3. Clients lockd contacts the local rpc.statd asking statd to monitor this system
4. Client’s statd replies to the local lockd that it is monitoring the client system
5. Client’s lockd contacts the server’s rpcbind to get port number of server’s lockd
6. Server’s rpcbind replies with the port number of the server’s lockd
7. Client’s lockd sends the lock request to the server’s lockd
8. Server’s lockd contacts its local statd asking statd to monitor the client system
9. Server’s statd replies to the local lockd that it now monitoring the client system
10. Server’s lockd forwards the lock request to the server’s kernel
11. Server’s kernel performs the lock and replies to the server’s lockd with status
12. Server’s lockd contacts the client’s rpcbind to get port number of client’s lockd
13. Client’s rpcbind replies with the port number of the client’s lockd
14. Server’s lockd sends the lock results back to the client’s lockd
15. Client’s lockd forwards these results back to the local kernel
16. Client’s kernel forwards the results back to the requesting application