From: "Sean Hefty" <sean.hefty@intel.com>
To: "'Steve Wise'" <swise@opengridcomputing.com>,
"Tom Tucker" <tom@opengridcomputing.com>
Cc: "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 14:36:46 -0700 [thread overview]
Message-ID: <000001c68f31$78910fe0$24268686@amr.corp.intel.com> (raw)
In-Reply-To: <1150230871.17394.68.camel@stevo-desktop>
>> 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.
- Sean
next prev parent reply other threads:[~2006-06-13 21:36 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 ` Sean Hefty [this message]
2006-06-13 21:46 ` [openib-general] " Steve Wise
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
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='000001c68f31$78910fe0$24268686@amr.corp.intel.com' \
--to=sean.hefty@intel.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=swise@opengridcomputing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®