Message-ID: <38E8695B.E99D0D6A@uow.edu.au>
Date:   Mon, 03 Apr 2000 09:50:19 +0000
From:   Andrew Morton <andrewm@uow.edu.au>
MIME-Version: 1.0
To:     kuznet@ms2.inr.ac.ru
CC:     netdev@oss.sgi.com
Subject: Re: coverage
References: <38E73398.E1727365@uow.edu.au> from "Andrew Morton" at Apr 2,
            0 04:13:15 pm <200004021618.UAA06079@ms2.inr.ac.ru>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-netdev@oss.sgi.com
Precedence: bulk

kuznet@ms2.inr.ac.ru wrote:
> 
> It is easy. "ping -f" does not create any real load on the network,
> it is pure latency test, when there is always only one packet in flight.

I use 'ping -l 100000'

     -l preload
             If preload is specified, ping sends that many packets as
fast as
             possible before falling into its normal mode of behavior. 
Only
             the super-user may use this option.

> Do not use it. Just write simple program, sending small udp packets
> without gaps, or use tools sort of netperf. To create extremal load,
> it is possible to use pgen tool by Robert Olsson
> (ftp://robur.slu.se:/pub/Linux/tmp/), it is a bit out of date,
> but easy to update.

Thanks - I'll look into it.

> >   - Tx stuck, invoke tx_timeout
> 
> I think any man working with network has in his table some broken hub,
> which generates only collisions. 8) Mmm... what will occur if to plug
> crossed pair to two hub slots? Will it simulate broken hub then?
> (I did not advise you to do this! 8))
> 
> Seriously, you can just to skip some TX ring refilling deliberately
> to trigger this condition.

Thanks again.

-- 
-akpm-