linux-toradex.git/include/linux/sunrpc/xprt.h, branch tegra-12r3

SUNRPC: Move the bound cred to struct rpc_rqst

2010-08-04T12:54:09+00:00

This will allow us to save the original generic cred in rpc_message, so
that if we migrate from one server to another, we can generate a new bound
cred without having to punt back to the NFS layer.

Signed-off-by: Trond Myklebust

SUNRPC: Move the task->tk_bytes_sent and tk_rtt to struct rpc_rqst

2010-05-14T19:09:36+00:00

It seems strange to maintain stats for bytes_sent in one structure, and
bytes received in another. Try to assemble all the RPC request-related
stats in struct rpc_rqst

Signed-off-by: Trond Myklebust

SUNRPC: Replace jiffies-based metrics with ktime-based metrics

2010-05-14T19:09:33+00:00

Currently RPC performance metrics that tabulate elapsed time use
jiffies time values.  This is problematic on systems that use slow
jiffies (for instance 100HZ systems built for paravirtualized
environments).  It is also a problem for computing precise latency
statistics for advanced network transports, such as InfiniBand,
that can have round-trip latencies significanly faster than a single
clock tick.

For the RPC client, adopt the high resolution time stamp mechanism
already used by the network layer and blktrace: ktime.

We use ktime format time stamps for all internal computations, and
convert to milliseconds for presentation.  As a result, we need only
addition operations in the performance critical paths; multiply/divide
is required only for presentation.

We could report RTT metrics in microseconds.  In fact the mountstats
format is versioned to accomodate exactly this kind of interface
improvement.

For now, however, we'll stay with millisecond precision for
presentation to maintain backwards compatibility with the handful of
currently deployed user space tools.  At a later point, we'll move to
an API such as BDI_STATS where a finer timestamp precision can be
reported.

Signed-off-by: Chuck Lever 
Signed-off-by: Trond Myklebust

SUNRPC: RPC metrics and RTT estimator should use same RTT value

2010-05-14T19:09:32+00:00

Compute an RPC request's RTT once, and use that value both for reporting
RPC metrics, and for adjusting the RTT context used by the RPC client's RTT
estimator algorithm.

Signed-off-by: Chuck Lever 
Signed-off-by: Trond Myklebust

SUNRPC: Fail over more quickly on connect errors

2010-05-14T19:09:30+00:00

We should not allow soft tasks to wait for longer than the major timeout
period when waiting for a reconnect to occur.

Remove the field xprt->connect_timeout since it has been obsoleted by
xprt->reestablish_timeout.

Signed-off-by: Trond Myklebust

nfsd41: sunrpc: add new xprt class for nfsv4.1 backchannel

2009-09-13T19:46:15+00:00

[sunrpc: change idle timeout value for the backchannel]
Signed-off-by: Alexandros Batsakis 
Signed-off-by: Benny Halevy 
Acked-by: Trond Myklebust 
Signed-off-by: J. Bruce Fields

nfsd41: sunrpc: Added rpc server-side backchannel handling

2009-09-11T19:04:16+00:00

When the call direction is a reply, copy the xid and call direction into the
req->rq_private_buf.head[0].iov_base otherwise rpc_verify_header returns
rpc_garbage.

Signed-off-by: Rahul Iyer 
Signed-off-by: Mike Sager 
Signed-off-by: Marc Eshel 
Signed-off-by: Benny Halevy 
Signed-off-by: Ricardo Labiaga 
Signed-off-by: Andy Adamson 
Signed-off-by: Benny Halevy 
[get rid of CONFIG_NFSD_V4_1]
[sunrpc: refactoring of svc_tcp_recvfrom]
[nfsd41: sunrpc: create common send routine for the fore and the back channels]
[nfsd41: sunrpc: Use free_page() to free server backchannel pages]
[nfsd41: sunrpc: Document server backchannel locking]
[nfsd41: sunrpc: remove bc_connect_worker()]
[nfsd41: sunrpc: Define xprt_server_backchannel()[
[nfsd41: sunrpc: remove bc_close and bc_init_auto_disconnect dummy functions]
[nfsd41: sunrpc: eliminate unneeded switch statement in xs_setup_tcp()]
[nfsd41: sunrpc: Don't auto close the server backchannel connection]
[nfsd41: sunrpc: Remove unused functions]
Signed-off-by: Alexandros Batsakis 
Signed-off-by: Ricardo Labiaga 
Signed-off-by: Benny Halevy 
[nfsd41: change bc_sock to bc_xprt]
[nfsd41: sunrpc: move struct rpc_buffer def into a common header file]
[nfsd41: sunrpc: use rpc_sleep in bc_send_request so not to block on mutex]
[removed cosmetic changes]
Signed-off-by: Benny Halevy 
[sunrpc: add new xprt class for nfsv4.1 backchannel]
[sunrpc: v2.1 change handling of auto_close and init_auto_disconnect operations for the nfsv4.1 backchannel]
Signed-off-by: Alexandros Batsakis 
[reverted more cosmetic leftovers]
[got rid of xprt_server_backchannel]
[separated "nfsd41: sunrpc: add new xprt class for nfsv4.1 backchannel"]
Signed-off-by: Benny Halevy 
Cc: Trond Myklebust 
[sunrpc: change idle timeout value for the backchannel]
Signed-off-by: Alexandros Batsakis 
Signed-off-by: Benny Halevy 
Acked-by: Trond Myklebust 
Signed-off-by: J. Bruce Fields

SUNRPC: Kill RPC_DISPLAY_ALL

2009-08-09T19:09:46+00:00

At some point, I recall that rpc_pipe_fs used RPC_DISPLAY_ALL.
Currently there are no uses of RPC_DISPLAY_ALL outside the transport
modules themselves, so we can safely get rid of it.

Signed-off-by: Chuck Lever 
Signed-off-by: Trond Myklebust

SUNRPC: Remove duplicate universal address generation

2009-08-09T19:09:35+00:00

RPC universal address generation is currently done in several places:
rpcb_clnt.c, nfs4proc.c xprtsock.c, and xprtrdma.c.  Remove the
redundant cases that convert a socket address to a universal
address.  The nfs4proc.c case takes a pre-formatted presentation
address string, not a socket address, so we'll leave that one.

Because the new uaddr constructor uses the recently introduced
rpc_ntop(), it now supports proper "::" shorthanding for IPv6
addresses.  This allows the kernel to register properly formed
universal addresses with the local rpcbind service, in _all_ cases.

The kernel can now also send properly formed universal addresses in
RPCB_GETADDR requests, and support link-local properly when
encoding and decoding IPv6 addresses.

Signed-off-by: Chuck Lever 
Signed-off-by: Trond Myklebust

nfs41: Rename rq_received to rq_reply_bytes_recvd

2009-06-17T21:11:40+00:00

The 'rq_received' member of 'struct rpc_rqst' is used to track when we
have received a reply to our request.  With v4.1, the backchannel
can now accept callback requests over the existing connection.  Rename
this field to make it clear that it is only used for tracking reply bytes
and not all bytes received on the connection.

Signed-off-by: Ricardo Labiaga 
Signed-off-by: Benny Halevy