From: Christoph Lameter <cl@linux-foundation.org>
To: David Miller <davem@davemloft.net>
Cc: 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 16:33:43 -0500 [thread overview]
Message-ID: <48A0B037.501@linux-foundation.org> (raw)
In-Reply-To: <20080811.141501.01468546.davem@davemloft.net>
David Miller wrote:
> Isn't that when some major scheduler changes went in? I'm not blaming
> the scheduler, but rather I'm making the point that there are other
> subsystems in the kernel that the networking interacts with that
> influences performance at such a low level. This includes the memory
> allocator :-)
Right this covers a significant portion of the kernel. SLAB was used since .22
was pretty early for SLUB. And around 2.6.24 we had the merges of the antifrag
logic.
.25 was the point where HR timers came in. By switching off hrtimers I can get
some (minor) portion of performance back. There must be more things in play
though.
Maybe what we are seeing is general bloat in kernel execution paths due to the
growth in complexity?
next prev parent reply other threads:[~2008-08-11 21:34 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 [this message]
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=48A0B037.501@linux-foundation.org \
--to=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 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).