All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: Anuj Kalia
	<anujkaliaiitd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: PCIe 2.0 motherboard + ConnectX-3 cards
Date: Sun, 24 Nov 2013 11:57:47 -0600	[thread overview]
Message-ID: <52923E1B.6000003@opengridcomputing.com> (raw)
In-Reply-To: <CADPSxAjCqk8GqQ9cQiceZk2fbrPuQdRWDoBSfkgLesVpVOc-fg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 11/22/2013 10:13 PM, Anuj Kalia wrote:
> Update: I found ways to improve active side performance from 10
> million RDMA writes per second to 20 million (which I believe is the
> PCIe bottleneck):
>
> 1. Use inline payload - I think this reduces PCIe traffic.

Yes, without inline, each IO requires 2 PCIe transactions:  1 to fetch 
(or push) the work request, and one to fetch the payload/data.  If you 
use inline, the data is included in the work request.  So you cut the 
required transactions in half.

> 2. Use non-signalled RDMA writes + don't poll for completion for every
> write - I don't know if ibv_poll_cq() uses the PCIe much.

Each signaled work request generates a completion entry (CQE) which is 
pushed from the adapter into the CQ in host memory.  So reducing the 
number of these required also reduces the PCIe transactions.

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:[~2013-11-24 17:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21 22:26 PCIe 2.0 motherboard + ConnectX-3 cards Anuj Kalia
     [not found] ` <CADPSxAhPhtMegUYmjVS6qZGsWVAbYKeOGRKz1CG9oK3S-pgD7w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-22  7:59   ` Anuj Kalia
     [not found]     ` <CADPSxAi06+_zjJ50v7CgCDzv+abDowN0pxBEgAZKwKBGPCe1ig-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-23  4:13       ` Anuj Kalia
     [not found]         ` <CADPSxAjCqk8GqQ9cQiceZk2fbrPuQdRWDoBSfkgLesVpVOc-fg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-24 17:57           ` Steve Wise [this message]
     [not found]             ` <52923E1B.6000003-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2013-11-26  2:08               ` Anuj Kalia

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=52923E1B.6000003@opengridcomputing.com \
    --to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
    --cc=anujkaliaiitd-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 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.