From: Bart Van Assche <bart.vanassche-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
To: Yuval Shaia <yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] IB/ipoib: CSUM support in connected mode
Date: Thu, 30 Jul 2015 19:03:22 -0700 [thread overview]
Message-ID: <55BAD76A.1070700@sandisk.com> (raw)
In-Reply-To: <20150730200907.GA3487@yuval-lab>
On 07/30/15 13:09, Yuval Shaia wrote:
> On Thu, Jul 30, 2015 at 09:38:54AM -0700, Bart Van Assche wrote:
>> On 07/30/2015 04:46 AM, Yuval Shaia wrote:
>>> struct ipoib_cm_data {
>>> __be32 qpn; /* High byte MUST be ignored on receive */
>>> __be32 mtu;
>>> + __be16 sig; /* must be IPOIB_CM_PROTO_SIG */
>>> + __be16 caps; /* 4 bits proto ver and 12 bits capabilities */
>>> };
>>
>> This patch modifies the private login data format that has been
>> standardized by the IETF in RFC 4755. Has this modification already
>> been discussed with the IETF ?
>>
> Yes.
Hello Yuval,
It should have been mentioned in the patch description that this patch
modifies the wire format, how it modifies the wire format, and also
which feedback (if any) has been received so far from the IETF.
Thanks,
Bart.
--
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:[~2015-07-31 2:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 11:46 [PATCH] IB/ipoib: CSUM support in connected mode Yuval Shaia
[not found] ` <1438256764-9077-1-git-send-email-yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2015-07-30 13:58 ` Yann Droneaud
[not found] ` <1438264693.9344.19.camel-RlY5vtjFyJ3QT0dZR+AlfA@public.gmane.org>
2015-07-30 15:20 ` Yuval Shaia
2015-07-30 15:51 ` Doug Ledford
[not found] ` <55BA47F0.5080504-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-07-30 17:15 ` Jason Gunthorpe
[not found] ` <20150730171538.GA25282-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2015-07-30 20:46 ` Yuval Shaia
2015-07-30 21:00 ` Jason Gunthorpe
[not found] ` <20150730210018.GA32451-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2015-11-18 20:27 ` Yuval Shaia
2015-11-23 18:29 ` Jason Gunthorpe
2015-07-30 20:37 ` Yuval Shaia
2015-11-18 10:46 ` Yuval Shaia
2015-11-24 9:45 ` Yann Droneaud
[not found] ` <1448358314.19858.13.camel-RlY5vtjFyJ3QT0dZR+AlfA@public.gmane.org>
2015-11-24 18:59 ` Jason Gunthorpe
2015-07-30 16:38 ` Bart Van Assche
[not found] ` <55BA531E.6060403-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2015-07-30 20:09 ` Yuval Shaia
2015-07-31 2:03 ` Bart Van Assche [this message]
[not found] ` <55BAD76A.1070700-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2015-09-03 20:29 ` Doug Ledford
[not found] ` <55E8ADB9.4090900-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-09-06 11:27 ` Yuval Shaia
2015-11-18 10:27 ` Yuval Shaia
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=55BAD76A.1070700@sandisk.com \
--to=bart.vanassche-xdaiopvojttbdgjk7y7tuq@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=yuval.shaia-QHcLZuEGTsvQT0dZR+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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).