From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Yann Droneaud <ydroneaud-RlY5vtjFyJ3QT0dZR+AlfA@public.gmane.org>,
"Hefty,
Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: rdma_get_cm_event() vs ibv_async_event()
Date: Tue, 29 Mar 2011 12:45:48 +0200 [thread overview]
Message-ID: <4D91B85C.1080106@mellanox.com> (raw)
In-Reply-To: <1301394815.2193.2.camel-H/AUWmsJYVeqvyCYKW+Xr6xOck334EZe@public.gmane.org>
Yann Droneaud wrote:
> So ignoring IBV_EVENT_COMM_EST async event seems the best option when
> using RDMA CM to establish connection ?
no! its a must for the rare case of repeated CM packet loss - Sean,
do you agree to that assertion? should the man page be more clear about
that?
Or.
--
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:[~2011-03-29 10:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1301052615.2192.15.camel@deela.quest-ce.net>
[not found] ` <1301059658.2192.23.camel@deela.quest-ce.net>
[not found] ` <1301059658.2192.23.camel-H/AUWmsJYVeqvyCYKW+Xr6xOck334EZe@public.gmane.org>
2011-03-29 9:37 ` rdma_get_cm_event() vs ibv_async_event() Yann Droneaud
[not found] ` <1301391461.2192.41.camel-H/AUWmsJYVeqvyCYKW+Xr6xOck334EZe@public.gmane.org>
2011-03-29 10:14 ` Or Gerlitz
[not found] ` <4D91B107.2040007-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2011-03-29 10:33 ` Yann Droneaud
[not found] ` <1301394815.2193.2.camel-H/AUWmsJYVeqvyCYKW+Xr6xOck334EZe@public.gmane.org>
2011-03-29 10:45 ` Or Gerlitz [this message]
[not found] ` <4D91B85C.1080106-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2011-03-29 14:51 ` Hefty, Sean
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=4D91B85C.1080106@mellanox.com \
--to=ogerlitz-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=ydroneaud-RlY5vtjFyJ3QT0dZR+AlfA@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 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.