After all I decided that best option actually would be to re-implement the
iperf logic inside the ovs-vlan-test python script itself, because of
following reasons:
1. flag "--tradeoff" (bidirectional, individual test) does not work for
TCP:
http://sourceforge.net/tracker/index.php?func=d
On Wed, Oct 19, 2011 at 6:55 PM, Ansis Atteka wrote:
>
> On Wed, Oct 19, 2011 at 6:33 PM, Jesse Gross wrote:
>>
>> On Wed, Oct 19, 2011 at 5:28 PM, Ethan Jackson wrote:
>> >> Implement ovs-vlan-test server logic so that it would restart iperf TCP
>> >> server every-time iperf-server exited becau
On Wed, Oct 19, 2011 at 6:33 PM, Jesse Gross wrote:
> On Wed, Oct 19, 2011 at 5:28 PM, Ethan Jackson wrote:
> >> Implement ovs-vlan-test server logic so that it would restart iperf TCP
> >> server every-time iperf-server exited because of this bug,
> >> For TCP (or maybe also for UDP) use a diff
On Wed, Oct 19, 2011 at 6:33 PM, Jesse Gross wrote:
> On Wed, Oct 19, 2011 at 5:28 PM, Ethan Jackson wrote:
>>> Implement ovs-vlan-test server logic so that it would restart iperf TCP
>>> server every-time iperf-server exited because of this bug,
>>> For TCP (or maybe also for UDP) use a differen
On Wed, Oct 19, 2011 at 5:28 PM, Ethan Jackson wrote:
>> Implement ovs-vlan-test server logic so that it would restart iperf TCP
>> server every-time iperf-server exited because of this bug,
>> For TCP (or maybe also for UDP) use a different tool (e.g. nttcp, netperf
>> ...). I suppose output from
> Here is a bug in iperf that stops me to solve TCP tests in a neat way:
> http://sourceforge.net/tracker/?func=detail&aid=1983829&group_id=128336&atid=711371.
> The problem is that iperf server silently exits after it has done
> bidirectional TCP mode testing with the client (when --tradeoff or
>
Here is a bug in iperf that stops me to solve TCP tests in a neat way:
http://sourceforge.net/tracker/?func=detail&aid=1983829&group_id=128336&atid=711371.
The problem is that iperf server silently exits after it has done
bidirectional TCP mode testing with the client (when --tradeoff or
--dualtest
Thanks for writing this up. I haven't read it closely yet.
I think using iperf to perform these tests is a great idea and the
right approach. So far, the patch looks like it will be a great
improvement over the existing code.
I'm not quite sure we are getting a great deal of value out of the
tw
Yes, running a TCP stream would generate MTU sized packets and should
detect pretty much all problems. The main reason for running UDP
tests with smaller packet size (include MTU sized ones) is to try to
narrow down the type of problem (i.e. to distinguish between an MTU
issue and a TSO issue). I
You could, however, compare TCP performance with and without a VLAN
being involved. Packet loss or out-of-order packets will show up as
performance loss.
On Wed, Oct 19, 2011 at 12:14:16PM -0700, Ansis Atteka wrote:
> Jesse,
>
> Potentially we could add iperf TCP tests to the ovs-vlan-test and t
Jesse,
Potentially we could add iperf TCP tests to the ovs-vlan-test and then IP
packet length would match MTU? Albeit then iperf would not report
packet-loss or out-of-order packet count.
During the implementation I had following concerns:
1. ovs-vlan-test utility uses iperf's STDOUT, STDERR
On Wed, Oct 19, 2011 at 11:59 AM, Ethan Jackson wrote:
>> * At least some of the problems that we have encountered are due to
>> offloading and some offloads are only available with TCP. Therefore,
>> running only UDP traffic won't catch these.
>
> Wouldn't iperf catch these errors, or are you s
> * At least some of the problems that we have encountered are due to
> offloading and some offloads are only available with TCP. Therefore,
> running only UDP traffic won't catch these.
Wouldn't iperf catch these errors, or are you suggesting that we craft
tcp datagrams by hand?
Ethan
On Tue, Oct 18, 2011 at 9:23 PM, Ansis Atteka wrote:
> ovs-vlan-test runs through a number of tests to identify VLAN issues. This
> is useful when trying to debug why a particular driver has issues, but it made
> the testing environment a bit harder to set up. This commit adds an iperf
> test to
On Tue, Oct 18, 2011 at 09:23:46PM -0700, Ansis Atteka wrote:
> ovs-vlan-test runs through a number of tests to identify VLAN issues. This
> is useful when trying to debug why a particular driver has issues, but it made
> the testing environment a bit harder to set up. This commit adds an iperf
>
ovs-vlan-test runs through a number of tests to identify VLAN issues. This
is useful when trying to debug why a particular driver has issues, but it made
the testing environment a bit harder to set up. This commit adds an iperf
test to check basic functionality. It also useful in detecting perfo
16 matches
Mail list logo
