linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: netdev@vger.kernel.org, lkml <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 11:50:57 -0700	[thread overview]
Message-ID: <48A08A11.8040507@intel.com> (raw)
In-Reply-To: <48A086B6.2000901@linux-foundation.org>

Christoph Lameter wrote:
> It seems that the network stack becomes slower over time? Here is a list of
> tbench results with various kernel versions:
> 
> 2.6.22		3207.77 mb/sec
> 2.6.24		3185.66
> 2.6.25		2848.83
> 2.6.26		2706.09
> 2.6.27(rc2)	2571.03
> 
> And linux-next is:
> 
> 2.6.28(l-next)	2568.74
> 
> It shows that there is still have work to be done on linux-next. Too close to
> upstream in performance.
> 
> Note the KT event between 2.6.24 and 2.6.25. Why is that?

is this with SLAB or with SLUB? SLUB has been known to impact network performance...

Auke



  reply	other threads:[~2008-08-11 18:53 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 [this message]
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
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=48A08A11.8040507@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=cl@linux-foundation.org \
    --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 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).