From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: 67-mjb2 vs 68-mjb1 (sdet degredation)
Date: Mon, 21 Apr 2003 14:12:08 -0700 [thread overview]
Message-ID: <1425480000.1050959528@flay> (raw)
Seem to loose about 2-3% on SDET syncing with 2.5.68. Not much change
apart from 67-68 changes. The merge of the ext2 alloc stuff has made
such a dramatic improvment for virgin 67-68, it's hard to see if
there was any degredation in mainline ;-) I had those in my tree before
though, so there should be much less change.
Just wondering if you can recognise / guess the problem from the profiles,
else I'll poke at it some more (will probably just work out what's hitting
.text.lock.filemap).
diffprofile {2.5.67-mjb2,2.5.68-mjb1}/sdetbench/128/profile
1307 2.1% total
432 0.0% .text.lock.filemap
269 0.8% default_idle
148 19.4% find_get_page
99 165.0% grab_block
97 26.6% __down
85 146.6% __brelse
78 22.2% do_no_page
75 625.0% update_atime
62 5.6% __d_lookup
61 103.4% task_mem
42 25.5% __wake_up
39 52.7% __mark_inode_dirty
38 211.1% read_inode_bitmap
32 0.0% group_reserve_blocks
31 79.5% generic_fillattr
...
-10 -6.0% kmap_atomic
-11 -26.8% truncate_inode_pages
-12 -26.1% ext2_free_blocks
-12 -5.2% do_page_fault
-13 -7.8% .text.lock.file_table
-13 -11.1% proc_check_root
-14 -19.7% dentry_open
-17 -4.1% .text.lock.namei
-17 -17.2% fget
-18 -10.3% .text.lock.attr
-21 -12.1% number
-24 -4.3% .text.lock.dcache
-27 -2.1% page_remove_rmap
-34 -54.8% ext2_new_block
-36 -3.4% atomic_dec_and_lock
-37 -3.1% copy_page_range
-57 -7.6% __copy_to_user_ll
-105 -95.5% task_vsize
-113 -96.6% find_trylock_page
next reply other threads:[~2003-04-21 21:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 21:12 Martin J. Bligh [this message]
2003-04-21 21:46 ` 67-mjb2 vs 68-mjb1 (sdet degredation) Andrew Morton
2003-04-21 22:55 ` William Lee Irwin III
2003-04-22 3:22 ` Martin J. Bligh
2003-04-22 3:52 ` Andrew Morton
2003-04-22 4:14 ` Martin J. Bligh
2003-04-22 4:06 ` Martin J. Bligh
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=1425480000.1050959528@flay \
--to=mbligh@aracnet.com \
--cc=akpm@digeo.com \
--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