netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: David Miller <davem@davemloft.net>,
	Netdev <netdev@vger.kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: AIM9 regression
Date: Tue, 23 Sep 2008 13:36:16 -0700	[thread overview]
Message-ID: <20080923133616.7d51c953@extreme> (raw)
In-Reply-To: <48D93203.2050204@linux-foundation.org>

On Tue, 23 Sep 2008 13:14:27 -0500
Christoph Lameter <cl@linux-foundation.org> wrote:

> I just dont seem to be able to get 2.6.27 to behave in a speedy way network
> wise. Configured out various components (netfilter, etc etc) but I still keep
> getting these aim9 result against 2.6.22:
> 
> 47 misc_rtns_1  448038.00 430118.00  -17920.00 -4.00% Auxiliary Loops/second
> 48 dir_rtns_1   2412587.41 2723000.00  310412.59 12.87% Directory
> Operations/second
> 49 shell_rtns_1 364.30 345.80     -18.50 -5.08% Shell Scripts/second
> 50 shell_rtns_2 364.20 355.34      -8.86 -2.43% Shell Scripts/second
> 51 shell_rtns_3 363.30 353.60      -9.70 -2.67% Shell Scripts/second
> 52 series_1     6694290.00 6706690.00   12400.00  0.19% Series Evaluations/second
> 53 shared_memory 1042900.00 1080630.00   37730.00  3.62% Shared Memory
> Operations/second
> 54 tcp_test     352035.00 278442.00  -73593.00 -20.91% TCP/IP Messages/second
> 55 udp_test     640940.00 585570.00  -55370.00 -8.64% UDP/IP DataGrams/second
> 56 fifo_test    772440.00 932330.00  159890.00 20.70% FIFO Messages/second
> 57 stream_pipe  1222870.00 1230140.00    7270.00  0.59% Stream Pipe
> Messages/second
> 58 dgram_pipe   1143106.89 1152730.00    9623.11  0.84% DataGram Pipe
> Messages/second
> 59 pipe_cpy     867850.00 1065430.00  197580.00 22.77% Pipe Messages/second
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Hardware configuration please?

  reply	other threads:[~2008-09-23 20:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-23 18:14 AIM9 regression Christoph Lameter
2008-09-23 20:36 ` Stephen Hemminger [this message]
2008-09-23 20:40   ` Christoph Lameter
2008-09-23 20:43     ` Christoph Lameter
2008-09-24  1:20     ` Jeff Garzik
2008-09-24  3:11       ` David Miller
2008-09-24 14:20         ` Christoph Lameter
2008-09-24  5:12 ` Herbert Xu
2008-09-24  5:18   ` David Miller
2008-09-24 15:16     ` Stephen Hemminger
2008-09-24 19:10       ` Christoph Lameter
2008-09-24 19:53         ` David Miller
2008-09-24 21:34           ` Stephen Hemminger
2008-09-24 22:26             ` David Miller
2008-09-24 19:36       ` David Miller
2008-09-29 14:24         ` Ilpo Järvinen
2008-09-29 14:54           ` Christoph Lameter
2008-09-29 15:12             ` Ilpo Järvinen
2008-09-29 15:36             ` Stephen Hemminger
2008-10-31 14:57             ` Ilpo Järvinen

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=20080923133616.7d51c953@extreme \
    --to=shemminger@vyatta.com \
    --cc=cl@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).