linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: "Martin J. Bligh" <mbligh@aracnet.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.0-test3-mm1
Date: Tue, 12 Aug 2003 01:17:48 +1000	[thread overview]
Message-ID: <200308120117.48938.kernel@kolivas.org> (raw)
In-Reply-To: <94490000.1060612530@[10.10.2.4]>

On Tue, 12 Aug 2003 00:35, Martin J. Bligh wrote:
> Degredation on kernbench is still there:
>
> Kernbench: (make -j N vmlinux, where N = 16 x num_cpus)
>                               Elapsed      System        User         CPU
>               2.6.0-test3       45.97      115.83      571.93     1494.50
>           2.6.0-test3-mm1       46.43      122.78      571.87     1496.00
>
> Quite a bit of extra sys time. I thought the suspected part of the sched
> changes got backed out, but maybe I'm just not following it ...

It was plus and minus. I've improved my hacks, but the A3 patch nanosecond 
timing will add extra overhead/locking. I'm not sure how you can compare 
these to the last ones you posted:

                              Elapsed      System        User         CPU
              2.6.0-test2       46.05      115.20      571.75     1491.25
          2.6.0-test2-con       46.98      121.02      583.55     1498.75
          2.6.0-test2-mm1       46.95      121.18      582.00     1497.50

I'll take a stab in the dark and say the nanosecond timing is a big part now. 
Backing out all the O*int patches in broken-out of 2.6.0-test3-mm1 should 
help identify that. 

I have an idea on how to trim the nanosecond overhead as well. The sched clock 
should be called if the timing is less than say two jiffies only. That will 
mean it will be called far less frequently.

Con

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2003-08-11 15:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-10  3:39 2.6.0-test3-mm1 Andrew Morton
2003-08-10 17:41 ` 2.6.0-test3-mm1 Thomas Schlichter
2003-08-11 18:26   ` 2.6.0-test3-mm1 George Anzinger
2003-08-13 20:18     ` 2.6.0-test3-mm1 Sam Ravnborg
2003-08-13 20:58       ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-14  8:17       ` 2.6.0-test3-mm1 and the -g thing George Anzinger
2003-08-11 14:03 ` 2.6.0-test3-mm1 Luiz Capitulino
2003-08-11 14:35 ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-11 15:17   ` Con Kolivas [this message]
2003-08-11 18:05   ` 2.6.0-test3-mm1 William Lee Irwin III
2003-08-11 18:57     ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-11 21:55     ` 2.6.0-test3-mm1 Con Kolivas
2003-08-11 22:19       ` 2.6.0-test3-mm1 William Lee Irwin III
2003-08-11 18:39   ` 2.6.0-test3-mm1 Andrew Morton
2003-08-11 20:17     ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-11 22:16       ` 2.6.0-test3-mm1 William Lee Irwin III
2003-08-11 22:50         ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-11 23:00           ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-11 23:39           ` 2.6.0-test3-mm1 William Lee Irwin III

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=200308120117.48938.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mbligh@aracnet.com \
    /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