linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: percpu-2.5.63-bk5-1 (properly generated)
Date: Sun, 02 Mar 2003 15:13:22 -0800	[thread overview]
Message-ID: <87420000.1046646801@[10.10.2.4]> (raw)
In-Reply-To: <20030302221037.GK1195@holomorphy.com>

>> Did you actually read the previous email? 
>> Same config file? Same tree? same compiler (gcc 2.95.4?)
> 
> gcc2.95.4; 2.5.63-bk5 w/& w/o, no patchkits prior, .config below

Wildly different config being compile tested => difference in speed.ls
 
>> I think we're talking about different things:
>> 1. Need to isolate what's causing the 6s improvement you're seeing.
>> Can you generate profiles & time output for before and after the patch,
>> and describe the test you're running (presumably make -j).
>> 2. SDET degredation. I'll try the additional patch you sent out on that.
> 
> It's not hard to figure out.

Part 2 may not be ... part 1 is ;-)

>>         60   125.0% page_address
>>         12    63.2% __pagevec_lru_add_active
>>         11    47.8% bad_range
>>         10    15.9% kmap_atomic
> 
> All users of page_zone(). The question you're (hopefully) about to
> answer is whether it was the division or something else like codesize
> or the newly introduced indirection.
> 
> If that is still seeing page_zone() suckage, I'll rip zone_table[] out
> of it entirely.

Still degraded: diffprofile:

       781     1.6% total
       346     1.0% default_idle
       217    10.1% __down
        79    12.0% __wake_up
        51    70.8% page_address
        32    66.7% kmap_atomic
        24     5.3% page_remove_rmap
        16    19.3% clear_page_tables
        14     4.6% release_pages
        13    33.3% path_release
        13     6.7% __copy_to_user_ll
        13   260.0% bad_range
        11     1.3% do_schedule
        10    15.6% pte_alloc_one

M.


  reply	other threads:[~2003-03-02 23:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-02 18:24 percpu-2.5.63-bk5-1 (properly generated) Martin J. Bligh
2003-03-02 20:24 ` William Lee Irwin III
2003-03-02 20:46   ` Martin J. Bligh
2003-03-02 21:06     ` William Lee Irwin III
2003-03-02 21:58       ` Martin J. Bligh
2003-03-02 22:10         ` William Lee Irwin III
2003-03-02 23:13           ` Martin J. Bligh [this message]
2003-03-02 23:42             ` William Lee Irwin III
2003-03-03  0:07               ` Martin J. Bligh
2003-03-03  1:43                 ` William Lee Irwin III
2003-03-03 17:40                   ` Martin J. Bligh
2003-03-03 22:51                     ` William Lee Irwin III
2003-03-03 23:30                       ` Martin J. Bligh
2003-03-04  0:14                         ` William Lee Irwin III
  -- strict thread matches above, loose matches on Subject: below --
2003-03-02 11:07 William Lee Irwin III
2003-03-02 13:15 ` 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='87420000.1046646801@[10.10.2.4]' \
    --to=mbligh@aracnet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.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;
as well as URLs for NNTP newsgroup(s).