From: Rick Jones <rick.jones2@hp.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: johnpol@2ka.mipt.ru, netdev@vger.kernel.org,
caitlinb@broadcom.com, kelly@au1.ibm.com, rusty@rustcorp.com.au
Subject: Re: Initial benchmarks of some VJ ideas [mmap memcpy vs copy_to_user].
Date: Thu, 11 May 2006 12:30:31 -0700 [thread overview]
Message-ID: <446390D7.8000709@hp.com> (raw)
In-Reply-To: <20060511.115409.89709859.davem@davemloft.net>
David S. Miller wrote:
> From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
> Date: Thu, 11 May 2006 20:18:15 +0400
>
>
>>Here is profile result:
>>1463625 78.0003 poll_idle
>>19171 1.0217 _spin_lock_irqsave
>>15887 0.8467 _read_lock
>>14712 0.7840 kfree
>>13370 0.7125 ip_frag_queue
>>11896 0.6340 delay_pmtmr
>>11811 0.6294 _spin_lock
>>11723 0.6247 csum_partial
>>11399 0.6075 ip_frag_destroy
>>11063 0.5896 serial_in
>>10533 0.5613 skb_release_data
>>10524 0.5609 ip_route_input
>>10319 0.5499 __alloc_skb
>
>
> Too bad spinlocks are not inlined any longer, this makes oprofile
> output so much less useful.
But it is nice to see how much time is being spent in "locking"
rick jones
next prev parent reply other threads:[~2006-05-11 19:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 12:24 Initial benchmarks of some VJ ideas [mmap memcpy vs copy_to_user] Evgeniy Polyakov
2006-05-08 19:51 ` Evgeniy Polyakov
2006-05-08 20:15 ` David S. Miller
2006-05-10 19:58 ` David S. Miller
2006-05-11 6:40 ` Evgeniy Polyakov
2006-05-11 7:07 ` David S. Miller
2006-05-11 8:30 ` Evgeniy Polyakov
2006-05-11 16:18 ` Evgeniy Polyakov
2006-05-11 18:54 ` David S. Miller
2006-05-11 19:30 ` Rick Jones [this message]
2006-05-12 7:54 ` Evgeniy Polyakov
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=446390D7.8000709@hp.com \
--to=rick.jones2@hp.com \
--cc=caitlinb@broadcom.com \
--cc=davem@davemloft.net \
--cc=johnpol@2ka.mipt.ru \
--cc=kelly@au1.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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).