From: Cliff Burdick <shaklee3@gmail.com>
To: "Xueming(Steven) Li" <xuemingl@mellanox.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] RDMA over DPDK
Date: Sun, 1 Mar 2020 07:31:24 -0800 [thread overview]
Message-ID: <CA+Gp1naFaR4ZqmiMNUD62BGoz3AqWpKLjuD3UwxwWrJX5LA=DQ@mail.gmail.com> (raw)
In-Reply-To: <VI1PR05MB3197A589C662EAF3C3B5FF4BACE60@VI1PR05MB3197.eurprd05.prod.outlook.com>
If you're interested in this for GPUs, you should check out cuVNF here:
https://developer.nvidia.com/aerial-sdk
On Sun, Mar 1, 2020 at 3:33 AM Xueming(Steven) Li <xuemingl@mellanox.com>
wrote:
> With a quick hack on mlx5 pmd, it's possible to send RDMA operation with
> few changes. Performance result between 25Gb back to back connected NICs:
>
> - Continues 1MB RDMA write on 256 different memory target of remote
> peer: line speed, 2.6Mpps, MTU 1024
> - Continues 8B RDMA write to remote peer: line speed, 29.4Mpps,
> RoCE2(74B+8B)
>
> Currently, dpdk usage focus on network scenario: ovs, firewall, load
> balance...
> With hw acceleration, RDMA is application level api with more capability
> than sockets, 2GB xfer, less latency and atomic operations, it will enable
> dpdk bypass stack to application server - another huge market I believe.
>
> Why RDMA over dpdk:
>
> - performance , dpdk style batch/burst xfer, less i-cache miss
> - easy to prefetch - no linked list
> - reuse mbuf data structure with some modification
> - able to send rdma request with eth mbuf data
> - virtualization support, with rte_flow, able to do hw encap/decap for VF
> RDMA traffic
>
> Potential application:
>
> - rdma <-> rdma application in DC/HPC
> - eth <-> rdma application
> - device power saving. If pc/mobile support rdma, playing video or
> download file, most networking xfer happens with few cpu involvement.
>
> Interested?
>
> Xueming Li
>
prev parent reply other threads:[~2020-03-01 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-01 11:33 Xueming(Steven) Li
2020-03-01 15:31 ` Cliff Burdick [this message]
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='CA+Gp1naFaR4ZqmiMNUD62BGoz3AqWpKLjuD3UwxwWrJX5LA=DQ@mail.gmail.com' \
--to=shaklee3@gmail.com \
--cc=users@dpdk.org \
--cc=xuemingl@mellanox.com \
/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).