public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Pradeep Satyanarayana <pradeeps-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Or Gerlitz <ogerlitz-smomgflXvOZWk0Htik3J/w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Moni Shoua <monis-smomgflXvOZWk0Htik3J/w@public.gmane.org>
Subject: Re: Crash in bonding
Date: Tue, 03 Nov 2009 08:38:22 -0800	[thread overview]
Message-ID: <4AF05C7E.3060804@linux.vnet.ibm.com> (raw)
In-Reply-To: <4AEFD866.1040106-smomgflXvOZWk0Htik3J/w@public.gmane.org>

Or Gerlitz wrote:
> Pradeep Satyanarayana wrote:
>> This crash was originally reported against Rhel5.4. However, one can
>> recreate this crash quite easily in OFED-1.5 too. 
> I understand that you get the crash when working with the RHEL5.4
> bonding driver, correct? 
We used the one that comes native with the Rhel5.4 distro. I also used installed
OFED-1.5 on Rhel5.4 and still see the same problem.

does it happen only with IPoIB devices acting
> as the bonding slaves or also with Ethernet devices? 

I am not exactly sure what you are hinting at. Simplest case is to use IPoIB
devices as slaves and with the steps below the crash occurs. The crash is specific
to IPoIB, and does not happen with Ethernet slaves.

Please note that
> with RHEL 5.4 there's no need to use the ofed provided bonding module,
> more over, I believe that the distro provided one is more stable and
> uptodate in this case. 
We used what is natively available with Rhel5.4.

Moving forward, ofed bonding support for newish
> distributions is to be removed. Moni, any reason to support bonding/EL
> 5.4 in ofed?

Can you explain why you plan to remove this from the newer distros? This is 
indeed news to me.

Pradeep

--
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

  parent reply	other threads:[~2009-11-03 16:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02 22:43 [Fwd: Crash in bonding] Pradeep Satyanarayana
     [not found] ` <4AEF60AC.6030508-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2009-11-03  7:14   ` Crash in bonding Or Gerlitz
     [not found]     ` <4AEFD866.1040106-smomgflXvOZWk0Htik3J/w@public.gmane.org>
2009-11-03 16:38       ` Pradeep Satyanarayana [this message]
     [not found]         ` <4AF05C7E.3060804-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2009-11-10 11:44           ` Or Gerlitz
     [not found] <4AEF6020.7000806@linux.vnet.ibm.com>
     [not found] ` <1257252696.13991.5.camel@linux-nzha.site>
     [not found]   ` <4AF05D9B.30807@linux.vnet.ibm.com>
     [not found]     ` <39C75744D164D948A170E9792AF8E7CA01AB635F@exil.voltaire.com>
     [not found]       ` <39C75744D164D948A170E9792AF8E7CA01AB635F-QfUkFaTmzUSUvQqKE/ONIwC/G2K4zDHf@public.gmane.org>
2009-11-03 17:40         ` Pradeep Satyanarayana

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=4AF05C7E.3060804@linux.vnet.ibm.com \
    --to=pradeeps-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=monis-smomgflXvOZWk0Htik3J/w@public.gmane.org \
    --cc=ogerlitz-smomgflXvOZWk0Htik3J/w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox