From: Ingo Molnar <mingo@elte.hu>
To: Nick Piggin <npiggin@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: lmbench ctxsw regression with CFS
Date: Sat, 4 Aug 2007 08:50:37 +0200 [thread overview]
Message-ID: <20070804065037.GA30816@elte.hu> (raw)
In-Reply-To: <20070803001447.GA14775@wotan.suse.de>
* Nick Piggin <npiggin@suse.de> wrote:
> Oh good. Thanks for getting to the bottom of it. We have normally
> disliked too much runtime tunables in the scheduler, so I assume these
> are mostly going away or under a CONFIG option for 2.6.23? Or...?
yeah, they are all already under CONFIG_SCHED_DEBUG. (it's just that the
add-on optimization is not upstream yet - the tunings are still being
tested) Btw., with SCHED_DEBUG we now also have your domain-tree sysctl
patch upstream, which has been in -mm for a near eternity.
> What CPU did you get these numbers on? Do the indirect calls hurt much
> on those without an indirect predictor? (I'll try running some tests).
it was on an older Athlon64 X2. I never saw indirect calls really
hurting on modern x86 CPUs - dont both CPU makers optimize them pretty
efficiently? (as long as the target function is always the same - which
it is here.)
> I must say that I don't really like the indirect calls a great deal,
> and they could be eliminated just with a couple of branches and direct
> calls.
yeah - i'll try that too. We can make the indirect call the uncommon
case and a NULL pointer be the common case, combined with a 'default',
direct function call. But i doubt it makes a big (or even measurable)
difference.
Ingo
next prev parent reply other threads:[~2007-08-04 6:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 2:15 lmbench ctxsw regression with CFS Nick Piggin
2007-08-02 2:31 ` Linus Torvalds
2007-08-02 2:41 ` Nick Piggin
2007-08-02 7:19 ` Ingo Molnar
2007-08-02 7:31 ` Nick Piggin
2007-08-02 15:44 ` Ingo Molnar
2007-08-03 0:14 ` Nick Piggin
2007-08-04 6:50 ` Ingo Molnar [this message]
2007-08-06 3:29 ` Nick Piggin
2007-08-13 12:30 ` Jens Axboe
2007-08-14 3:00 ` Andrew Morton
2007-08-14 3:23 ` Nick Piggin
2007-08-16 21:28 ` Siddha, Suresh B
2007-08-14 3:25 ` David Miller
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=20070804065037.GA30816@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=torvalds@linux-foundation.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.