diff options
author | Chuck Lever <chuck.lever@oracle.com> | 2010-05-07 13:34:17 -0400 |
---|---|---|
committer | Trond Myklebust <Trond.Myklebust@netapp.com> | 2010-05-14 15:09:32 -0400 |
commit | 9bc4e3ca46e4eb9cb434de4175c6041d00bbdca3 (patch) | |
tree | a1677884fe5779008243a083f7a8455f43990c0a /net | |
parent | dfe52c0419b8324bacd69bd28aae77e2d6ee0379 (diff) | |
download | linux-9bc4e3ca46e4eb9cb434de4175c6041d00bbdca3.tar.gz linux-9bc4e3ca46e4eb9cb434de4175c6041d00bbdca3.tar.bz2 linux-9bc4e3ca46e4eb9cb434de4175c6041d00bbdca3.zip |
NFS: Calldata for nfs4_renew_done()
I'm about to change task->tk_start from a jiffies value to a ktime_t
value in order to make RPC RTT reporting more precise.
Recently (commit dc96aef9) nfs4_renew_done() started to reference
task->tk_start so that a jiffies value no longer had to be passed
from nfs4_proc_async_renew(). This allowed the calldata to point to
an nfs_client instead.
Changing task->tk_start to a ktime_t value makes it effectively
useless for renew timestamps, so we need to restore the pre-dc96aef9
logic that provided a jiffies "start" timestamp to nfs4_renew_done().
Both an nfs_client pointer and a timestamp need to be passed to
nfs4_renew_done(), so create a new nfs_renewdata structure that
contains both, resembling what is already done for delegreturn,
lock, and unlock.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions