On Wed, 20 Jul 2005 11:31 am, Jesper Juhl wrote: > On 7/20/05, Daniel Walker <[EMAIL PROTECTED]> wrote: > > On Wed, 2005-07-20 at 11:04 +1000, Con Kolivas wrote: > > > On Wed, 20 Jul 2005 10:23 am, Daniel Walker wrote: > > > > On Wed, 2005-07-20 at 00:32 +0200, Ingo Molnar wrote: > > > > > - networking is another frequent source of latencies - it might > > > > > make sense to add a workload doing lots of socket IO. (localhost > > > > > might be enough, but not for everything) > > > > > > > > The Gnutella test? > > > > > > I've seen some massive latencies on mainline when throwing network > > > loads from outside, but with my limited knowledge I haven't found a way > > > to implement such a thing locally. I'll look at this gnutella test at > > > some stage to see what it is and if I can adopt the load within > > > interbench. Thanks for the suggestion. > > > > There isn't actually a test called "The Gnutella test" , but I think > > Gnutella clients put lots of network load on a system (Lee was talking > > about that not to long ago). I was thinking that type of load may have > > been what Ingo was talking about. > > If you want to generate a lot of network related interrupts, wouldn't > a much simpler way to do that be a simple > > ping -f targetbox > > from a host connected to `targetbox' via a crosswired ethernet cable > or a fast switch..? > > Also easy to modify the size of the ping packets if you want to.
Well that load works very well, but once again it isn't really something that can be done locally on one box running init 1. Cheers, Con - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
