public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: 丁定华 <dingdinghua85-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: two questions about RDMA-WRITE
Date: Tue, 13 Apr 2010 09:50:20 -0500	[thread overview]
Message-ID: <4BC484AC.80804@opengridcomputing.com> (raw)
In-Reply-To: <q2v7bb361261004130308za7b4d6ccj6fdb657b7c7cc7e9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

丁定华 wrote:
> Hi guys:
> I'm doing a project using RDMA to transfer data between servers.  I'm
> using RDMA_PS_TCP type and do RDMA_WRITE operations from client node
> to server node. While the program succeed in setting up connection and
> transferring data, I 'm still very confused about two problems:
> (1)  After transfer the data using IB_WR_RDMA_WRITE , the complete
> queue entry found that the opcode turned from IB_WR_RDMA_WRITE to
> IB_WR_RDMA_WRITE_WITH_IMM, I don't know the meaning of this opcode and
> the reason of the change.
>   

The opcode in the completion is of type enum ib_wc_opcode, not enum
ib_wr_opcode. You are mis-interpreting the opcode in the completion.

> (2)  It takes a long time to finish rdma_disconnect work (about 10
> seconds), so is it a reasonable time?
>   

What device are you using?


Steve.
--
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:[~2010-04-13 14:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-13 10:08 two questions about RDMA-WRITE 丁定华
     [not found] ` <q2v7bb361261004130308za7b4d6ccj6fdb657b7c7cc7e9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-04-13 14:50   ` Steve Wise [this message]
     [not found]     ` <4BC484AC.80804-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-04-14  2:15       ` Ding Dinghua
2010-04-13 15:48   ` Sean Hefty
     [not found]     ` <77BFFFE3D9C34D64A03DA5A9DC22F42D-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2010-04-14  3:56       ` Ding Dinghua
     [not found]         ` <20100414034142.GA5567-6UwBTAaVBkEeWBJJgrHO4P1unptsbck7@public.gmane.org>
2010-04-15 17:17           ` Sean Hefty
     [not found]             ` <4B0EDAC5753E48CD8CE32B6E3EF15949-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2010-04-21 12:37               ` Ding Dinghua

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=4BC484AC.80804@opengridcomputing.com \
    --to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
    --cc=dingdinghua85-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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