On 11/18/2010 11:36 AM, Steve Wise wrote:
On 11/17/2010 07:12 PM, Roland Dreier wrote:
> > Nov 15 09:39:00 node4 kernel: rpcrdma: connection to
> > 192.168.0.100:20049 on mlx4_0, memreg 5 slots 32 ird 16
> >
> > and then 5 minutes later:
> >
> > Nov 15 09:44:00 node4 kernel: rpcrdma: connection to
> > 192.168.0.100:20049 closed (-103)
> >
> >
>
> I think NFSRDMA server will close the connection after 5 minutes of
> inactivity...
Should the code be spamming the logs for normal events? (Or is this
with an elevated log level)
IMO its not needed. From net/sunrpx/xprtrdma/verbs.c (nfsrdma client):
[r...@r10 xprtrdma]# grep "connection to" *.c
verbs.c: printk(KERN_INFO "rpcrdma: connection to %pI4:%u "
verbs.c: printk(KERN_INFO "rpcrdma: connection to %pI4:%u
closed (%d)\n",
[r...@r10 xprtrdma]#
Looks like its surrounded by #ifdef RPC_DEBUG though. And RPC_DEBUG
seems to be always turned on:
From include/linux/sunrpc/debug.h:
/*
* Enable RPC debugging/profiling.
*/
#ifdef CONFIG_SYSCTL
#define RPC_DEBUG
#endif
However, maybe these two printk's should just be dprintks...
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
