diff options
| author | Ricardo Labiaga <Ricardo.Labiaga@netapp.com> | 2009-04-01 09:22:53 -0400 |
|---|---|---|
| committer | Benny Halevy <bhalevy@panasas.com> | 2009-06-17 15:43:45 -0400 |
| commit | 18dca02aeb3c49dfce87c76be643b139d05cf647 (patch) | |
| tree | 3e261efdba69b967500a36d8f65ac643c8693d76 /drivers/char/hvc_iseries.c | |
| parent | 34dc1ad752ad3f55b2a6e6cd8cfcf3504682fec7 (diff) | |
nfs41: Add ability to read RPC call direction on TCP stream.
NFSv4.1 callbacks can arrive over an existing connection. This patch adds
the logic to read the RPC call direction (call or reply). It does this by
updating the state machine to look for the call direction invoking
xs_tcp_read_calldir(...) after reading the XID.
[nfs41: Keep track of RPC call/reply direction with a flag]
As per 11/14/08 review of RFC 53/85.
Add a new flag to track whether the incoming message is an RPC call or an
RPC reply. TCP_RPC_REPLY is set in the 'struct sock_xprt' tcp_flags in
xs_tcp_read_calldir() if the message is an RPC reply sent on the forechannel.
It is cleared if the message is an RPC request sent on the back channel.
Signed-off-by: Ricardo Labiaga <Ricardo.Labiaga@netapp.com>
Signed-off-by: Benny Halevy <bhalevy@panasas.com>
Diffstat (limited to 'drivers/char/hvc_iseries.c')
0 files changed, 0 insertions, 0 deletions