From: Yann Droneaud <ydroneaud-RlY5vtjFyJ3QT0dZR+AlfA@public.gmane.org>
To: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: "Hefty,
Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: RDMA CM: private_data_len
Date: Mon, 28 Mar 2011 11:46:14 +0200 [thread overview]
Message-ID: <1301305574.804.1.camel@dworkin.quest-ce.net> (raw)
In-Reply-To: <4D904B52.5000004-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Le lundi 28 mars 2011 à 10:48 +0200, Or Gerlitz a écrit :
> Yann Droneaud wrote:
> > On a client, rdma_connect() returns -1 and set errno EINVAL if
> > struct rdma_conn_param->private_data_len is set to something higher than
> > 56 bytes.
> >
> > But on a server, using rdma_accept() with struct
> > rdma_conn_param->private_data_len is set to 64 (for example) didn't
> > return any error.
> >
> > What is the maximum data size that can be exchanged between peers at
> > connection time, and where to find its definition (at compile time or at
> > runtime) ?
>
> yep, this isn't clear from the librdmacm man pages see the patch
> that follows.
Oh yes, it's clear now.
Thanks for the patch and the link to IB specs.
Regards.
--
Yann Droneaud
OPTEYA
--
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
prev parent reply other threads:[~2011-03-28 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 18:27 RDMA CM: private_data_len Yann Droneaud
[not found] ` <1301077661.2192.31.camel-H/AUWmsJYVeqvyCYKW+Xr6xOck334EZe@public.gmane.org>
2011-03-28 8:48 ` Or Gerlitz
[not found] ` <4D904B52.5000004-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2011-03-28 9:46 ` Yann Droneaud [this message]
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=1301305574.804.1.camel@dworkin.quest-ce.net \
--to=ydroneaud-rly5vtjfyj3qt0dzr+alfa@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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