All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Pearson <rpearsonhpe@gmail.com>
To: Yanjun Zhu <yanjun.zhu@linux.dev>,
	"Pearson, Robert B" <robert.pearson2@hpe.com>,
	Christian Blume <chr.blume@gmail.com>,
	RDMA mailing list <linux-rdma@vger.kernel.org>
Subject: Re: Soft-RoCE performance
Date: Fri, 11 Feb 2022 11:48:46 -0600	[thread overview]
Message-ID: <6ea9199c-bae4-bfde-e45a-a6cda9acd58b@gmail.com> (raw)
In-Reply-To: <11e71fc4-6194-9290-df0e-f062af91cc8c@linux.dev>

On 2/10/22 08:04, Yanjun Zhu wrote:

> 
> Thanks, I have also reached the big bandwidth with the same methods.
> How about latency of soft roce?
> 
> Zhu Yanjun

In loopback on my system with ib_write_lat I see the following. It isn't very exciting. The use case I am interested in doesn't require super low latency though.


 #bytes #iterations    t_min[usec]    t_max[usec]  t_typical[usec]    t_avg[usec]    t_stdev[usec]   99% percentile[usec]   99.9% percentile[usec] 

 2       1000          1.57           9.65         1.84     	       2.04        	0.69   		5.02    		9.65   

 4       1000          1.58           7.89         1.82     	       1.99        	0.54   		4.68    		7.89   

 8       1000          1.60           6.86         1.79     	       1.95        	0.51   		4.08    		6.86   

 16      1000          1.59           5.28         1.83     	       1.95        	0.42   		3.72    		5.28   

 32      1000          1.64           8.18         1.84     	       1.99        	0.52   		4.07    		8.18   

 64      1000          1.65           8.58         1.84     	       1.99        	0.48   		3.92    		8.58   

 128     1000          1.80           10.58        1.96     	       2.10        	0.47   		3.94    		10.58  

 256     1000          1.76           12.54        2.00     	       2.17        	0.52   		4.00    		12.54  

 512     1000          1.69           11.09        1.95     	       2.21        	0.66   		3.97    		11.09  

 1024    1000          1.80           12.91        2.00     	       2.22        	0.56   		3.89    		12.91  

 2048    1000          2.04           9.29         2.20     	       2.37        	0.50   		4.03    		9.29   

 4096    1000          2.39           11.66        2.58     	       2.76        	0.56   		4.67    		11.66  


  parent reply	other threads:[~2022-02-11 17:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10  3:33 Soft-RoCE performance Christian Blume
2022-02-10  5:13 ` Pearson, Robert B
2022-02-10  5:28   ` Pearson, Robert B
2022-02-10 14:04   ` Yanjun Zhu
2022-02-10 22:23     ` Christian Blume
2022-02-11 17:48     ` Bob Pearson [this message]
2022-02-11 10:53   ` Bernard Metzler

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=6ea9199c-bae4-bfde-e45a-a6cda9acd58b@gmail.com \
    --to=rpearsonhpe@gmail.com \
    --cc=chr.blume@gmail.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=robert.pearson2@hpe.com \
    --cc=yanjun.zhu@linux.dev \
    /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.