public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: dwalker@mvista.com, Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, ck@vds.kolivas.org
Subject: Re: Interbench real time benchmark results
Date: Wed, 20 Jul 2005 11:45:39 +1000	[thread overview]
Message-ID: <200507201145.39378.kernel@kolivas.org> (raw)
In-Reply-To: <9a8748490507191831267b17d9@mail.gmail.com>

On Wed, 20 Jul 2005 11:31 am, Jesper Juhl wrote:
> On 7/20/05, Daniel Walker <dwalker@mvista.com> 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

  reply	other threads:[~2005-07-20  1:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19 22:16 Interbench real time benchmark results Con Kolivas
2005-07-19 22:32 ` Ingo Molnar
2005-07-20  0:23   ` Daniel Walker
2005-07-20  1:04     ` Con Kolivas
2005-07-20  1:22       ` Daniel Walker
2005-07-20  1:31         ` Jesper Juhl
2005-07-20  1:45           ` Con Kolivas [this message]
2005-07-21  4:48         ` 2.6.12 PREEMPT_RT && PPC john cooper
2005-07-21 11:45           ` Gene Heskett
2005-07-21 12:22             ` Gene Heskett
2005-07-21 13:13             ` john cooper
2005-07-26 12:00           ` Ingo Molnar
2005-07-26 14:44             ` K.R. Foley
2005-07-26 14:55               ` Ingo Molnar
2005-07-26 15:06                 ` K.R. Foley
2005-07-20  0:23 ` Interbench real time benchmark results Daniel Walker
2005-07-20  4:59 ` Lee Revell

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=200507201145.39378.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=ck@vds.kolivas.org \
    --cc=dwalker@mvista.com \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox