From: Nick Piggin <piggin@cyberone.com.au>
To: Con Kolivas <kernel@kolivas.org>
Cc: Cliff White <cliffw@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.0-test2-mm3 osdl-aim-7 regression
Date: Thu, 07 Aug 2003 15:11:52 +1000 [thread overview]
Message-ID: <3F31DF98.6020908@cyberone.com.au> (raw)
In-Reply-To: <200308071240.54863.kernel@kolivas.org>
Con Kolivas wrote:
>On Thu, 7 Aug 2003 05:10, Cliff White wrote:
>
>>>Binary searching (insert gratuitous rant about benchmarks that take more
>>>than two minutes to complete) reveals that the slowdown is due to
>>>sched-2.6.0-test2-mm2-A3.
>>>
>
>This is most likely the round robinning of tasks every 25ms. The extra
>overhead of nanosecond timing I doubt could make that size difference (but I
>could be wrong). There is some tweaking of this round robinning in my code
>which may help this, but it won't bring it back up to original performance I
>believe. Two things to try are add my patches up to O12.3int first to see how
>much (if at all!) it helps, and change TIMESLICE_GRANULARITY in sched.c to
>(MAX_TIMESLICE) which basically disables it completely. If there is still a
>drop in performance with this, the remainder is the extra locking/overhead in
>nanosecond timing.
>
>
What is the need for this round robining? Don't processes get a calculated
timeslice anyway?
next prev parent reply other threads:[~2003-08-07 5:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 16:07 2.6.0-test2-mm3 osdl-aim-7 regression Cliff White
2003-08-06 5:23 ` Andrew Morton
2003-08-06 19:10 ` Cliff White
2003-08-07 2:40 ` Con Kolivas
2003-08-07 5:11 ` Nick Piggin [this message]
2003-08-07 5:41 ` Con Kolivas
2003-08-07 8:25 ` Nick Piggin
2003-08-07 10:01 ` Con Kolivas
2003-08-07 10:05 ` Nick Piggin
2003-08-08 20:58 ` Cliff White
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=3F31DF98.6020908@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--cc=cliffw@osdl.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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