public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test4-mm1
Date: Mon, 25 Aug 2003 16:10:42 -0700	[thread overview]
Message-ID: <30190000.1061853042@flay> (raw)
In-Reply-To: <20030824171318.4acf1182.akpm@osdl.org>

System time is still rather higher in kernbench, though maybe the
elapsed time isn't degraded so much any more. Not sure if this is
scheduler changes or not, but last time, we isolated a change of
exactly this magnitude to one of those patches (Ingo's IIRC).

I tried "set TIMESLICE_GRANULARITY to MAX_TIMESLICE in sched.c" as
requested, makes no difference really (-max result below).

Kernbench: (make -j vmlinux, maximal tasks)
                              Elapsed      System        User         CPU
              2.6.0-test4       45.87      116.92      571.10     1499.00
          2.6.0-test4-mm1       46.29      121.39      570.52     1494.75
      2.6.0-test4-mm1-max       46.00      122.18      570.73     1505.75

diffprofile:

      7763     4.8% total
      2921     6.4% default_idle
       949     0.0% direct_strnlen_user
       719    20.6% __copy_from_user_ll
       554    10.4% __copy_to_user_ll
       544    33.5% kmem_cache_free
       425     0.0% kpmd_ctor
       372    26.1% schedule
       349    18.7% atomic_dec_and_lock
       322     4.1% __d_lookup
       318     8.6% find_get_page
       283   165.5% may_open
       279     1.2% page_remove_rmap
       275    16.0% buffered_rmqueue
       263    42.4% __wake_up
       212    15.3% free_hot_cold_page
       119     6.4% path_lookup
       117     3.7% zap_pte_range
       114     0.0% direct_strncpy_from_user
       107    17.3% generic_file_open
...
      -102    -1.6% page_add_rmap
      -122  -100.0% strncpy_from_user
      -288   -79.8% dentry_open
      -305   -66.2% do_page_cache_readahead
      -353  -100.0% pgd_ctor
      -447   -80.4% file_ra_state_init
      -558   -74.9% filp_close
      -854  -100.0% strnlen_user


  parent reply	other threads:[~2003-08-25 23:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-25  0:13 2.6.0-test4-mm1 Andrew Morton
2003-08-25  6:16 ` pcnet32 oops patches (was Re: 2.6.0-test4-mm1) Barry K. Nathan
2003-08-25 11:00   ` Domen Puncer
2003-08-25 17:30 ` 2.6.0-test4-mm1: wl3501_cs.c doesn't compile Adrian Bunk
2003-08-25 17:46   ` Arnaldo Carvalho de Melo
2003-08-25 18:24     ` Arnaldo Carvalho de Melo
2003-08-25 18:39       ` Arnaldo Carvalho de Melo
2003-08-25 22:01         ` Adrian Bunk
2003-08-26 15:22           ` Arnaldo Carvalho de Melo
2003-08-25 19:37 ` [BUG] 2.6.0-test4-mm1: NFS+XFS=data corruption Barry K. Nathan
2003-08-25 19:45   ` Andrew Morton
2003-08-25 22:54     ` Steve Lord
2003-08-26 10:14       ` Andrew Morton
2003-08-26 11:01         ` Suparna Bhattacharya
2003-08-26 17:44           ` Andrew Morton
2003-08-26 17:57             ` Steve Lord
2003-08-26 18:34               ` Andrew Morton
2003-08-25 23:10 ` Martin J. Bligh [this message]
2003-08-26 10:08   ` 2.6.0-test4-mm1 William Lee Irwin III
2003-08-26 14:23     ` 2.6.0-test4-mm1 Martin J. Bligh
2003-08-26 14:32       ` 2.6.0-test4-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=30190000.1061853042@flay \
    --to=mbligh@aracnet.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@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