All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Wise <swise@opengridcomputing.com>
To: Sean Hefty <sean.hefty@intel.com>
Cc: Tom Tucker <tom@opengridcomputing.com>,
	Andrew Morton <akpm@osdl.org>,
	netdev@vger.kernel.org, rdreier@cisco.com,
	linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: RE: [openib-general] [PATCH v2 1/2] iWARP Connection Manager.
Date: Tue, 13 Jun 2006 16:46:36 -0500	[thread overview]
Message-ID: <1150235196.17394.91.camel@stevo-desktop> (raw)
In-Reply-To: <000001c68f31$78910fe0$24268686@amr.corp.intel.com>

On Tue, 2006-06-13 at 14:36 -0700, Sean Hefty wrote:
> >> Er...no. It will lose this event. Depending on the event...the carnage
> >> varies. We'll take a look at this.
> >>
> >
> >This behavior is consistent with the Infiniband CM (see
> >drivers/infiniband/core/cm.c function cm_recv_handler()).  But I think
> >we should at least log an error because a lost event will usually stall
> >the rdma connection.
> 
> I believe that there's a difference here.  For the Infiniband CM, an allocation
> error behaves the same as if the received MAD were lost or dropped.  Since MADs
> are unreliable anyway, it's not so much that an IB CM event gets lost, as it
> doesn't ever occur.  A remote CM should retry the send, which hopefully allows
> the connection to make forward progress.
> 

hmm.  Ok.  I see.  I misunderstood the code in cm_recv_handler().

Tom and I have been talking about what we can do to not drop the event.
Stay tuned.

Steve.


  reply	other threads:[~2006-06-13 21:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-07 20:06 [PATCH v2 0/2][RFC] iWARP Core Support Steve Wise
2006-06-07 20:06 ` [PATCH v2 1/2] iWARP Connection Manager Steve Wise
2006-06-08  7:54   ` Andrew Morton
2006-06-12 15:54     ` Tom Tucker
2006-06-13 20:34       ` Steve Wise
2006-06-13 21:36         ` [openib-general] " Sean Hefty
2006-06-13 21:46           ` Steve Wise [this message]
2006-06-14 16:11             ` Steve Wise
2006-06-07 20:06 ` [PATCH v2 2/2] iWARP Core Changes Steve Wise
2006-06-07 22:13   ` Tom Tucker
  -- strict thread matches above, loose matches on Subject: below --
2006-06-14 18:06 [openib-general] [PATCH v2 1/2] iWARP Connection Manager Caitlin Bestler

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=1150235196.17394.91.camel@stevo-desktop \
    --to=swise@opengridcomputing.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=openib-general@openib.org \
    --cc=rdreier@cisco.com \
    --cc=sean.hefty@intel.com \
    --cc=tom@opengridcomputing.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.