From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: lihaidong <lihaidong-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Problems using krping
Date: Tue, 26 Jan 2010 09:01:24 -0600 [thread overview]
Message-ID: <4B5F03C4.1070705@opengridcomputing.com> (raw)
In-Reply-To: <201001261339589687690-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
lihaidong wrote:
> Mr.Wise
> ||| else {
> |||
> ||| cb->rdma_sq_wr.opcode = IB_WR_RDMA_READ;
> ||| if (cb->mem == FASTREG) {
> ||| /*
> ||| * Immediately follow the read with a
> ||| * fenced LOCAL_INV.
> ||| */
> ||| cb->rdma_sq_wr.next = &inv;
> ||| memset(&inv, 0, sizeof inv);
> ||| inv.opcode = IB_WR_LOCAL_INV;
> ||| inv.ex.invalidate_rkey = cb->fastreg_mr->rkey;
> ||| inv.send_flags = IB_SEND_FENCE;
> ||| }
> ||| }
> |||
> ||| ret = ib_post_send(cb->qp, &cb->rdma_sq_wr, &bad_wr);
> ||| if (ret) {
> ||| printk(KERN_ERR PFX "post send error %d\n", ret);
> ||| break;
> ||| }
> ||| cb->rdma_sq_wr.next = NULL;
> the last line, is that safe? There's an invalidate wr following
> rdma_sq_wr.This line will not disturb invalidate wr being performed in
> lower level, right?
>
Correct. The work requests are copied by the verbs layer. So once you
return from ib_post_send, the send work request structure itself can be
reused/freed/whatever.
--
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:[~2010-01-26 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201001211807011710722@inspur.com>
[not found] ` <201001211807011710722-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
2010-01-21 14:40 ` Problems using krping Steve Wise
[not found] ` <201001221533186875550@inspur.com>
[not found] ` <201001221533186875550-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
2010-01-22 15:16 ` Steve Wise
[not found] ` <201001242242553436345@inspur.com>
[not found] ` <201001242242553436345-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
2010-01-24 21:44 ` Steve Wise
[not found] ` <201001251036131874884@inspur.com>
[not found] ` <201001251036131874884-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
2010-01-25 3:28 ` Steve Wise
[not found] ` <201001261339589687690@inspur.com>
[not found] ` <201001261339589687690-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
2010-01-26 15:01 ` Steve Wise [this message]
[not found] ` <201001262046537030587@inspur.com>
[not found] ` <201001262046537030587-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
2010-01-26 15:02 ` Steve Wise
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=4B5F03C4.1070705@opengridcomputing.com \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=lihaidong-6gUaA8visnnQT0dZR+AlfA@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 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.