All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: "Sean Hefty" <sean.hefty@intel.com>
Cc: <general@lists.openfabrics.org>, <linux-kernel@vger.kernel.org>,
	<netdev@vger.kernel.org>
Subject: Re: [ofa-general] InfiniBand/RDMA merge plans for 2.6.24
Date: Thu, 13 Sep 2007 14:02:57 -0700	[thread overview]
Message-ID: <adatzpyl1mm.fsf@cisco.com> (raw)
In-Reply-To: <000401c7f632$c993e8e0$65cc180a@amr.corp.intel.com> (Sean Hefty's message of "Thu, 13 Sep 2007 11:20:38 -0700")

 > > - My user_mad P_Key index support patch.  I'll test the ioctl to
 > >   change to the new mode and merge this I guess, since Hal and Sean
 > >   have tested this out.
 > 
 > I can give this patch a reviewed-by: too, and I will also try to review a couple
 > of the pending ipoib patches.

Thanks!

 > > - Sean's QoS changes.  These look fine at first glance, and I just
 > >   plan to understand the backwards compatibility story (ie how this
 > >   works with an old SM) and merge.  Anyone who objects let me know.
 > 
 > The new QoS fields fall into fields that are currently reserved, which should be
 > ignored by an older SM.  I've only tested this against openSM however.

That seems OK -- I'm OK with breaking things if an SM is clearly buggy
(and not ignoring fields that are defined to be ignored in the spec
would certainly be a clear bug to me).

 > This patch was generated in response to an Intel MPI issue.  We've seen MPI take
 > several minutes to respond to a connection request during the middle of large
 > application runs.  When this happens, the active side times out the connection.
 > In OFED, we added module parameters to adjust the rdma_cm connection timeout on
 > the active side, but I believe that sending an MRA from the passive side is a
 > better solution.

OK -- just to make sure I'm understanding what you're saying: have you
confirmed that your proposed patches actually fix the issue?

 - R.

  reply	other threads:[~2007-09-13 21:03 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13 17:57 InfiniBand/RDMA merge plans for 2.6.24 Roland Dreier
2007-09-13 18:04 ` [ofa-general] " Steve Wise
2007-09-13 18:56   ` Jeff Garzik
2007-09-13 18:59     ` Steve Wise
2007-09-13 19:55       ` Jeff Garzik
2007-09-14 12:55       ` Evgeniy Polyakov
2007-09-13 21:12     ` Roland Dreier
2007-09-13 21:11   ` Roland Dreier
2007-09-13 22:59     ` Michael Chan
2007-09-14 16:18       ` Roland Dreier
2007-09-14 21:09         ` Michael Chan
2007-09-15 14:03     ` Steve Wise
2007-09-13 18:20 ` Sean Hefty
2007-09-13 21:02   ` Roland Dreier [this message]
2007-09-14 17:45     ` Sean Hefty
2007-10-02 18:26       ` Roland Dreier
2007-10-02 18:50         ` Sean Hefty
2007-10-05 23:10           ` Roland Dreier
     [not found]   ` <1190034015.6272.83.camel@hrosenstock-ws.xsigo.com>
2007-09-18  9:48     ` Tziporet Koren
2007-09-13 18:22 ` Shirley Ma
2007-09-13 21:00   ` Roland Dreier
2007-09-16  8:50 ` [ofa-general] " Or Gerlitz
2007-09-17 22:11   ` Roland Dreier
2007-09-18  7:09 ` Jack Morgenstein
2007-09-18 16:34 ` Michael S. Tsirkin
2007-09-18 17:18   ` Roland Dreier
2007-09-18 17:22     ` Michael S. Tsirkin

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=adatzpyl1mm.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=general@lists.openfabrics.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sean.hefty@intel.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.