From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: Stephen Cousins <steve.cousins-e7X0jjDqjFGHXe+LvDLADg@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: mxl4 and rpcrdma: connection to 192.168.0.100:20049 on mlx4_0, memreg 5 slots 32 ird 16
Date: Wed, 17 Nov 2010 11:43:52 -0600 [thread overview]
Message-ID: <4CE41458.7020202@opengridcomputing.com> (raw)
In-Reply-To: <AANLkTi=d6d2vydtcK+ux22e-QR5xqrkenMoeM8AzHBVq-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 11/15/2010 05:29 PM, Stephen Cousins wrote:
> The 2.7.700 firmware is brand new from Supermicro. Prior to this it
> was 2.7.0 and it showed the same thing.
>
> NFS is working for the most part but the client always logs messages
> like below after a modestly sizable transfer ( like 2GB) with dd:
>
> # dd if=/dev/zero of=node4.dat bs=1M count=2K oflag=direct
> 2048+0 records in
> 2048+0 records out
> 2147483648 bytes (2.1 GB) copied, 11.7277 seconds, 183 MB/s
>
> messages.log:
>
> 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...
Steve.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-11-17 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 23:29 mxl4 and rpcrdma: connection to 192.168.0.100:20049 on mlx4_0, memreg 5 slots 32 ird 16 Stephen Cousins
[not found] ` <AANLkTi=d6d2vydtcK+ux22e-QR5xqrkenMoeM8AzHBVq-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-11-17 17:43 ` Steve Wise [this message]
[not found] ` <4CE41458.7020202-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-11-18 1:03 ` Stephen Cousins
2010-11-18 1:12 ` Roland Dreier
[not found] ` <ada62vvigdx.fsf-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2010-11-18 17:36 ` Steve Wise
[not found] ` <4CE5640F.6040005-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-11-18 17:41 ` Steve Wise
[not found] ` <4CE56538.3040700-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-11-18 19:22 ` Roland Dreier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CE41458.7020202@opengridcomputing.com \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=steve.cousins-e7X0jjDqjFGHXe+LvDLADg@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.