public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: frank zago <fzago-klaOcWyJdxkshyMvu7JE4pqQE7yCjDx5@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [RFC] RDMA CM + XRC, take two
Date: Wed, 11 May 2011 09:42:15 -0500	[thread overview]
Message-ID: <4DCAA047.2040904@systemfabricworks.com> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A82373BBE2-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>

Hello Sean,

On 05/10/2011 06:17 PM, Hefty, Sean wrote:
>> This is an improved version of my previous patch to add XRC support to
>> RDMA CM.
> 
> I would still like to see support merged upstream and into mainline libibverbs before applying this to my tree.

Agreed. 

>  
>> This version now support the newer rdma CM interface. It needs some
>> polishing but it works.
> 
> It's hard to comment on the patch as an attachment.  In several places, if/else statements were added, but indentation was not added to the opposite part of the statement.  There was also a rather large amount of code added to rdma_create_qp() that needs to be split into a separate function.  (I dislike functions longer than a screen.)

Sorry for that attachment. I tried several time to post inline patches but was always getting a mangled patch.
I'll address you comments in a new patch.

>  
>> It modifies the rdma_client/server examples to use xrc instead of rc.
>>
>> The big hack is that the SRQ number needs to be transmitted to the remote
>> side. This patch hijacks the private data, so it's not acceptable. Ideally the SRQ
>> number should be transmitted either in the REQ or REP packet (depending
>> on which side the sender or the receiver) alongside the QP number. But that
>> would need a change in the specs. Any suggestions ?
> 
> What are the QPNs carried in the REQ and REP?

Those for the XRC QPs. Same as a for regular RC connection.

Frank.
--
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

  parent reply	other threads:[~2011-05-11 14:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09 22:33 [RFC] RDMA CM + XRC, take two frank zago
     [not found] ` <4DC86BB2.1020002-klaOcWyJdxkshyMvu7JE4pqQE7yCjDx5@public.gmane.org>
2011-05-10 23:17   ` Hefty, Sean
     [not found]     ` <1828884A29C6694DAF28B7E6B8A82373BBE2-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-05-11 14:42       ` frank zago [this message]
     [not found]         ` <4DCAA047.2040904-klaOcWyJdxkshyMvu7JE4pqQE7yCjDx5@public.gmane.org>
2011-05-11 15:03           ` Hefty, Sean
     [not found]             ` <1828884A29C6694DAF28B7E6B8A82373BC59-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-05-11 18:36               ` frank zago
     [not found]                 ` <4DCAD746.7050606-klaOcWyJdxkshyMvu7JE4pqQE7yCjDx5@public.gmane.org>
2011-05-11 19:08                   ` Hefty, Sean
     [not found]                     ` <1828884A29C6694DAF28B7E6B8A82373BE79-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-05-11 19:36                       ` Bob Pearson
     [not found]                         ` <9ECD201D-0CD8-4339-81E0-163FC130C705-klaOcWyJdxkshyMvu7JE4pqQE7yCjDx5@public.gmane.org>
2011-05-11 23:23                           ` Bob Pearson
2011-05-11 23:47                           ` Hefty, Sean
2011-05-12 22:33   ` Hefty, Sean
     [not found]     ` <1828884A29C6694DAF28B7E6B8A82373F23B-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-05-13  6:16       ` Bob Pearson
     [not found]         ` <984CAD75-D012-4725-B294-99B1AF32E49B-klaOcWyJdxkshyMvu7JE4pqQE7yCjDx5@public.gmane.org>
2011-05-13 14:39           ` 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=4DCAA047.2040904@systemfabricworks.com \
    --to=fzago-klaocwyjdxkshymvu7je4pqqe7ycjdx5@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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