From: Jeff Becker <jeffrey.c.becker@nasa.gov>
To: Steve Wise <swise@opengridcomputing.com>
Cc: Yan Burman <yanb@mellanox.com>,
"bfields@fieldses.org" <bfields@fieldses.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Or Gerlitz <ogerlitz@mellanox.com>,
Tom Tucker <tom@opengridcomputing.com>
Subject: Re: NFS over RDMA crashing
Date: Wed, 6 Feb 2013 09:06:52 -0800 [thread overview]
Message-ID: <51128DAC.9000206@nasa.gov> (raw)
In-Reply-To: <51127DB1.6070804@opengridcomputing.com>
Hi. In case you're interested, I did the NFS/RDMA backports for OFED. I
tested that NFS/RDMA in OFED 3.5 works on kernel 3.5, and also the RHEL
6.3 kernel. However, I did not test it with SRIOV. If you test it
(OFED-3.5-rc6 was released last week), I'd like to know how it goes. Thanks.
Jeff Becker
On 02/06/2013 07:58 AM, Steve Wise wrote:
> On 2/6/2013 9:48 AM, Yan Burman wrote:
>> When I moved to commit 79f77bf9a4e3dd5ead006b8f17e7c4ff07d8374e I was
>> no longer getting the server crashes,
>> so the reset of my tests were done using that point (it is somewhere
>> in the middle of 3.7.0-rc2)
>>
> +tom tucker
>
> I'd try going back a few kernels, like to 3.5.x and see if things are
> more stable. If you find a point that works, then git bisect might help
> identify the regression.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Becker <jeffrey.c.becker-NSQ8wuThN14@public.gmane.org>
To: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
Cc: Yan Burman <yanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
"bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org"
<bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>,
"linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
Tom Tucker
<tom-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
Subject: Re: NFS over RDMA crashing
Date: Wed, 6 Feb 2013 09:06:52 -0800 [thread overview]
Message-ID: <51128DAC.9000206@nasa.gov> (raw)
In-Reply-To: <51127DB1.6070804-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
Hi. In case you're interested, I did the NFS/RDMA backports for OFED. I
tested that NFS/RDMA in OFED 3.5 works on kernel 3.5, and also the RHEL
6.3 kernel. However, I did not test it with SRIOV. If you test it
(OFED-3.5-rc6 was released last week), I'd like to know how it goes. Thanks.
Jeff Becker
On 02/06/2013 07:58 AM, Steve Wise wrote:
> On 2/6/2013 9:48 AM, Yan Burman wrote:
>> When I moved to commit 79f77bf9a4e3dd5ead006b8f17e7c4ff07d8374e I was
>> no longer getting the server crashes,
>> so the reset of my tests were done using that point (it is somewhere
>> in the middle of 3.7.0-rc2)
>>
> +tom tucker
>
> I'd try going back a few kernels, like to 3.5.x and see if things are
> more stable. If you find a point that works, then git bisect might help
> identify the regression.
> --
> 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
--
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:[~2013-02-06 17:27 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 15:48 NFS over RDMA crashing Yan Burman
2013-02-06 15:48 ` Yan Burman
2013-02-06 15:58 ` Steve Wise
2013-02-06 15:58 ` Steve Wise
2013-02-06 17:06 ` Jeff Becker [this message]
2013-02-06 17:06 ` Jeff Becker
2013-02-07 15:54 ` Yan Burman
2013-02-07 15:54 ` Yan Burman
2013-02-06 22:24 ` J. Bruce Fields
2013-02-06 22:24 ` J. Bruce Fields
2013-02-06 22:28 ` Steve Wise
2013-02-06 22:28 ` Steve Wise
2013-02-08 5:37 ` Tom Tucker
2013-02-08 5:37 ` Tom Tucker
2013-02-07 16:41 ` J. Bruce Fields
2013-02-07 16:41 ` J. Bruce Fields
2013-02-11 15:19 ` Yan Burman
2013-02-11 15:19 ` Yan Burman
2013-02-11 18:13 ` J. Bruce Fields
2013-02-11 18:13 ` J. Bruce Fields
2013-02-15 15:27 ` J. Bruce Fields
2013-02-15 15:27 ` J. Bruce Fields
2013-02-18 11:44 ` Yan Burman
2013-02-18 11:44 ` Yan Burman
2014-03-07 16:59 ` Steve Wise
2014-03-07 16:59 ` Steve Wise
2014-03-07 20:41 ` Steve Wise
2014-03-07 20:41 ` Steve Wise
2014-03-08 16:39 ` Steve Wise
2014-03-08 16:39 ` Steve Wise
2014-03-08 19:20 ` Steve Wise
2014-03-08 19:20 ` Steve Wise
2014-03-08 20:13 ` Steve Wise
2014-03-08 20:13 ` Steve Wise
2014-03-12 13:33 ` Jeff Layton
2014-03-12 13:33 ` Jeff Layton
2014-03-12 14:05 ` Trond Myklebust
2014-03-12 14:05 ` Trond Myklebust
2014-03-12 14:22 ` Tom Tucker
2014-03-12 14:22 ` Tom Tucker
2014-03-12 14:28 ` Jeffrey Layton
2014-03-12 14:28 ` Jeffrey Layton
2014-03-12 15:03 ` Trond Myklebust
2014-03-12 15:03 ` Trond Myklebust
2014-03-12 15:29 ` Jeffrey Layton
2014-03-12 15:29 ` Jeffrey Layton
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=51128DAC.9000206@nasa.gov \
--to=jeffrey.c.becker@nasa.gov \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=swise@opengridcomputing.com \
--cc=tom@opengridcomputing.com \
--cc=yanb@mellanox.com \
/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.