From: Leon Romanovsky <leon@kernel.org>
To: QWang <3100102071@zju.edu.cn>
Cc: linux-rdma@vger.kernel.org
Subject: Re: Why our soft-RoCE throughput is quite low compared with TCP
Date: Fri, 15 Nov 2019 18:07:07 +0200 [thread overview]
Message-ID: <20191115160707.GG6763@unreal> (raw)
In-Reply-To: <f97b72b6-4def-2970-c9f6-f11b97d5378e@zju.edu.cn>
On Fri, Nov 15, 2019 at 09:26:41PM +0800, QWang wrote:
> Dear experts on RDMA,
> We are sorry to disturb you. Because of a project, we need to
> integrate soft-RoCE in our system. However ,we are very confused by our
> soft-RoCE throughput results, which are quite low compared with TCP
> throughput. The throughput of soft-RoCE in our tests measured by ib_send_bw
> and ib_read_bw is only 2 Gbps (the net link bandwidth is 100 Gbps and the
> two Xeon E5 servers with Mellanox ConnectX-4 cards are connected via
> back-to-back, the OS is ubuntu16.04 with kernel 4.15.0-041500-generic). The
> throughput of hard-RoCE and TCP are normal, which are 100 Gbps and 20 Gbps,
> respectively. But in the figure 6 in the attached paper "A Performance
> Comparison of Container Networking Alternatives", the throughput of
> soft-RoCE can be up to 23 Gbps. In our tests, we get the open-source
> soft-RoCE from github in https://github.com/linux-rdma. Do you know how can
> we get such high bandwidth? Do we need to configure some OS system settings?
> We find that in 2017, someone finds the same problem and he posts all
> his detailed results on https://bugzilla.kernel.org/show_bug.cgi?id=190951
> . But it remains unsolved. His results are nearly the same with our's. For
> simplicity, we do not post our results in this email. You can get very
> detailed information in the web page listed above.
> We are very confused by our results. We will very appreciate it if we
> can receive your early reply. Best wishes,
> Wang Qi
Can you please fix your email client?
The email text looks like one big sentence.
From the perf report attached to this bugzilla, looks like RXE does a
lot of CRC32 calculations and it is consistent with what Matan said
a long time ago, RXE "stuck" in ICRC calculations required by spec.
I'm curios what are your CONFIG_CRYPTO_* configs?
Thanks
>
next prev parent reply other threads:[~2019-11-15 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 13:26 Why our soft-RoCE throughput is quite low compared with TCP QWang
2019-11-15 16:07 ` Leon Romanovsky [this message]
2019-11-18 6:38 ` [question]Why " wangqi
2019-11-18 9:49 ` Leon Romanovsky
2019-11-18 10:13 ` wangqi
2019-11-18 12:28 ` Leon Romanovsky
2019-11-18 12:56 ` wangqi
2019-11-18 14:41 ` Leon Romanovsky
2019-11-19 0:22 ` wangqi
2019-11-19 7:38 ` Leon Romanovsky
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=20191115160707.GG6763@unreal \
--to=leon@kernel.org \
--cc=3100102071@zju.edu.cn \
--cc=linux-rdma@vger.kernel.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.