From: Dipankar Sarma <dipankar@in.ibm.com>
To: William Lee Irwin III <wli@holomorphy.com>,
Zwane Mwaikambo <zwane@linuxpower.ca>,
Andrew Morton <akpm@digeo.com>,
lkml <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: 2.5.38-mm3
Date: Fri, 27 Sep 2002 13:57:43 +0530 [thread overview]
Message-ID: <20020927135743.B25021@in.ibm.com> (raw)
In-Reply-To: <20020926133919.GQ3530@holomorphy.com>; from wli@holomorphy.com on Thu, Sep 26, 2002 at 06:39:19AM -0700
On Thu, Sep 26, 2002 at 06:39:19AM -0700, William Lee Irwin III wrote:
> Interesting, can you narrow down the poll overheads any? No immediate
> needs (read as: leave your box up, but watch for it when you can),
> but I'd be interested in knowing if it's fd chunk or poll table setup
> overhead.
Hmm.. I don't see this by just leaving the box up (and a fiew interactive
commands) (4CPU P3 2.5.38-vanilla) -
8744695 default_idle 136635.8594
4371 __rdtsc_delay 136.5938
22793 do_softirq 118.7135
1734 serial_in 21.6750
261 .text.lock.serio 13.7368
8777715 total 6.2461
422 tasklet_hi_action 2.0288
106 bh_action 1.3250
46 system_call 1.0455
56 __generic_copy_to_user 0.8750
575 timer_bh 0.8168
70 __cpu_up 0.7292
57 cpu_idle 0.5089
24 __const_udelay 0.3750
35 mdio_read 0.3646
120 probe_irq_on 0.3571
134 page_remove_rmap 0.3102
108 page_add_rmap 0.3068
18 find_get_page 0.2812
189 do_wp_page 0.2513
7 fput 0.2188
27 pte_alloc_one 0.1875
135 __free_pages_ok 0.1834
2 syscall_call 0.1818
11 pgd_alloc 0.1719
11 __free_pages 0.1719
65 i8042_interrupt 0.1693
8 __wake_up 0.1667
16 find_vma 0.1667
15 serial_out 0.1562
15 radix_tree_lookup 0.1339
17 kmem_cache_free 0.1328
17 get_page_state 0.1328
62 zap_pte_range 0.1292
6 mdio_sync 0.1250
3 ret_from_intr 0.1250
2 cap_inode_permission_lite 0.1250
2 cap_file_permission 0.1250
49 do_anonymous_page 0.1178
9 lru_cache_add 0.1125
9 fget 0.1125
What application were you all running ?
Thanks
--
Dipankar Sarma <dipankar@in.ibm.com> http://lse.sourceforge.net
Linux Technology Center, IBM Software Lab, Bangalore, India.
next prev parent reply other threads:[~2002-09-27 8:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 7:57 2.5.38-mm3 Andrew Morton
2002-09-26 12:24 ` 2.5.38-mm3 Dipankar Sarma
2002-09-26 12:29 ` 2.5.38-mm3 William Lee Irwin III
2002-09-26 12:40 ` 2.5.38-mm3 Dipankar Sarma
2002-09-26 12:42 ` 2.5.38-mm3 William Lee Irwin III
2002-09-26 13:05 ` 2.5.38-mm3 Dipankar Sarma
2002-09-26 13:17 ` 2.5.38-mm3 William Lee Irwin III
2002-09-26 13:29 ` 2.5.38-mm3 Zwane Mwaikambo
2002-09-26 13:39 ` 2.5.38-mm3 William Lee Irwin III
2002-09-26 13:46 ` 2.5.38-mm3 Zwane Mwaikambo
2002-09-27 8:27 ` Dipankar Sarma [this message]
2002-09-27 9:20 ` 2.5.38-mm3 William Lee Irwin III
2002-09-27 9:58 ` 2.5.38-mm3 Dipankar Sarma
2002-09-27 15:04 ` 2.5.38-mm3 Martin J. Bligh
2002-09-27 17:14 ` 2.5.38-mm3 Dipankar Sarma
2002-09-27 22:54 ` 2.5.38-mm3 William Lee Irwin III
2002-09-28 5:41 ` 2.5.38-mm3 Dipankar Sarma
2002-09-28 4:35 ` 2.5.38-mm3 Zwane Mwaikambo
2002-09-28 4:36 ` 2.5.38-mm3 William Lee Irwin III
2002-09-28 4:54 ` 2.5.38-mm3 Zwane Mwaikambo
2002-09-28 5:29 ` 2.5.38-mm3 Dipankar Sarma
2002-09-28 4:30 ` 2.5.38-mm3 Zwane Mwaikambo
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=20020927135743.B25021@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wli@holomorphy.com \
--cc=zwane@linuxpower.ca \
/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).