netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [Netperf PATCH] output remote_send_size in TCP_MAERTS result
@ 2012-12-14 10:49 Amos Kong
  2012-12-14 21:27 ` Rick Jones
  0 siblings, 1 reply; 2+ messages in thread
From: Amos Kong @ 2012-12-14 10:49 UTC (permalink / raw)
  To: rick.jones2; +Cc: netdev, Amos Kong

When I executed TCP_MAERTS by following command line:
  netperf-2.6.0 -H 192.168.58.23 -l 10 -C -t TCP_MAERTS -- -m 512,1024
The outputed send size is '512'.

When I executed TCP_MAERTS by following command line:
  netperf-2.6.0 -H 192.168.58.23 -l 10 -t TCP_MAERTS -- -m 512,1024
The outputed send size is '1024'.

In TCP_MAERTS test, we should output the remote send size '1024',
this patch fixed this issue.

Reported-by: Wenli Quan <wquan@redhat.com>
Signed-off-by: Amos Kong <akong@redhat.com>
---
 src/nettest_omni.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/nettest_omni.c b/src/nettest_omni.c
index 826167a..b0b1500 100644
--- a/src/nettest_omni.c
+++ b/src/nettest_omni.c
@@ -5951,7 +5951,7 @@ Size (bytes)\n\
 		cpu_fmt_1,		/* the format string */
 		rsr_size,		/* remote recvbuf size */
 		lss_size,		/* local sendbuf size */
-		send_size,		/* how large were the recvs */
+		remote_send_size,	/* how large were the recvs */
 		elapsed_time,		/* how long was the test */
 		thruput, 		/* what was the xfer rate */
 		local_cpu_utilization,	/* local cpu */
@@ -5983,7 +5983,7 @@ Size (bytes)\n\
 		tput_fmt_1,		/* the format string */
 		lsr_size, 		/* local recvbuf size */
 		rss_size, 		/* remot sendbuf size */
-		remote_send_size,		/* how large were the recvs */
+		remote_send_size,	/* how large were the recvs */
 		elapsed_time, 		/* how long did it take */
 		thruput,                  /* how fast did it go */
 		((print_headers) ||
-- 
1.7.1

^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [Netperf PATCH] output remote_send_size in TCP_MAERTS result
  2012-12-14 10:49 [Netperf PATCH] output remote_send_size in TCP_MAERTS result Amos Kong
@ 2012-12-14 21:27 ` Rick Jones
  0 siblings, 0 replies; 2+ messages in thread
From: Rick Jones @ 2012-12-14 21:27 UTC (permalink / raw)
  To: Amos Kong; +Cc: netdev

On 12/14/2012 02:49 AM, Amos Kong wrote:
> When I executed TCP_MAERTS by following command line:
>    netperf-2.6.0 -H 192.168.58.23 -l 10 -C -t TCP_MAERTS -- -m 512,1024
> The outputed send size is '512'.
>
> When I executed TCP_MAERTS by following command line:
>    netperf-2.6.0 -H 192.168.58.23 -l 10 -t TCP_MAERTS -- -m 512,1024
> The outputed send size is '1024'.
>
> In TCP_MAERTS test, we should output the remote send size '1024',
> this patch fixed this issue.

Hi Amos -

While I suspect at least a few folks on the netdev list are interested 
in "things netperf," netperf is not maintained via the netdev list. 
There are two lists hosted on netperf.org which pertain to "things 
netperf."  The first is netperf-talk which is geared towards users.  The 
second netperf-dev which is geared towards those developing netperf.

No need to re-post there this time (though feel free to for the 
archives), I've gone ahead and applied the fix to the netperf top-of-trunk.

happy benchmarking,

rick jones

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-12-14 21:27 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-12-14 10:49 [Netperf PATCH] output remote_send_size in TCP_MAERTS result Amos Kong
2012-12-14 21:27 ` Rick Jones

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).