All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: "Kok, Auke" <auke-jan.h.kok@intel.com>
Cc: David Miller <davem@davemloft.net>,
	cl@linux-foundation.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: tbench regression on each kernel release from 2.6.22 -> 2.6.28
Date: Mon, 11 Aug 2008 15:11:17 -0700	[thread overview]
Message-ID: <48A0B905.20603@hp.com> (raw)
In-Reply-To: <48A0B571.7010903@intel.com>

Kok, Auke wrote:
> David Miller wrote:
> 
>>From: Christoph Lameter <cl@linux-foundation.org>
>>Date: Mon, 11 Aug 2008 16:33:43 -0500
>>
>>
>>>Maybe what we are seeing is general bloat in kernel execution paths
>>>due to the growth in complexity?
>>
>>It could be, and any kind of analysis into this would be great.
> 
> 
> perhaps Rick Jones who maintains netperf could enlighten us on some historic
> numbers? he usually seems to be happy to prop up new netperf numbers :)

While this is an excellent opening to talk about how netperf 
top-of-trunk can now emit keyword=value results easier (ostensibly) to 
put into a database then the regular or even CSV output formats, I 
cannot fully exploit it by pointing at a database of results :(

rick jones

  reply	other threads:[~2008-08-11 22:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-11 18:36 tbench regression on each kernel release from 2.6.22 -> 2.6.28 Christoph Lameter
2008-08-11 18:50 ` Kok, Auke
2008-08-11 18:56   ` Christoph Lameter
2008-08-11 21:15 ` David Miller
2008-08-11 21:33   ` Christoph Lameter
2008-08-11 21:50     ` David Miller
2008-08-11 21:56       ` Kok, Auke
2008-08-11 22:11         ` Rick Jones [this message]
2008-08-12  7:11     ` Andi Kleen
2008-08-12 18:57       ` Christoph Lameter
2008-08-12  8:13   ` Ilpo Järvinen
2008-08-18  2:05     ` Zhang, Yanmin
2008-08-18  7:53       ` Ilpo Järvinen
2008-08-19  0:56         ` Zhang, Yanmin
2008-08-18 14:07       ` Christoph Lameter
2008-08-18 14:31         ` Ray Lee
2008-08-18 14:34           ` Christoph Lameter
2008-08-19  1:01         ` Zhang, Yanmin
2008-08-18  1:48 ` Zhang, Yanmin

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=48A0B905.20603@hp.com \
    --to=rick.jones2@hp.com \
    --cc=auke-jan.h.kok@intel.com \
    --cc=cl@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.