From: Andrew Gallatin <gallatin@myri.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, robert@robur.slu.se
Subject: Re: CPU utilization increased in 2.6.27rc
Date: Wed, 13 Aug 2008 12:13:40 -0400 [thread overview]
Message-ID: <48A30834.4090802@myri.com> (raw)
In-Reply-To: <20080812.181549.229367205.davem@davemloft.net>
David Miller wrote:
> From: Andrew Gallatin <gallatin@myri.com>
> Date: Tue, 12 Aug 2008 20:56:23 -0400
>
>> pkt_sched: Schedule qdiscs instead of netdev_queue.
>
> While I'm waiting for your beforehand profile data,
> here is a stab in the dark patch which might fix
> the problem.
>
> Robert, this could explain some of the things in the
> multiqueue testing profile you sent me a week or so
> ago.
>
> Let me know how well it works:
Excellent! This completely fixes the increased CPU
utilization I observed on both 10GbE and 1GbE interfaces,
and CPU utilization is now reduced back to 2.6.26 levels.
Oprofile now is nearly identical to what it was prior to
37437bb2e1ae8af470dfcd5b4ff454110894ccaf:
8363 6.5081 vmlinux _raw_spin_lock
5612 4.3672 oprofiled (no symbols)
4420 3.4396 ehci_hcd (no symbols)
4325 3.3657 vmlinux handle_IRQ_event
3688 2.8700 vmlinux default_idle
3164 2.4622 vmlinux nv_start_xmit_optimized
3092 2.4062 vmlinux sk_run_filter
3072 2.3906 vmlinux tcp_ack
2969 2.3105 vmlinux __copy_skb_header
2453 1.9089 vmlinux kmem_cache_free
2400 1.8677 vmlinux IRQ0x69_interrupt
2295 1.7860 vmlinux nv_rx_process_optimized
2092 1.6280 vmlinux kmem_cache_alloc
2072 1.6124 vmlinux kfree
2049 1.5945 vmlinux packet_rcv_spkt
1984 1.5439 vmlinux __tcp_push_pending_frames
1942 1.5113 vmlinux nv_nic_irq_optimized
1933 1.5043 vmlinux _raw_spin_unlock
1637 1.2739 vmlinux nv_tx_done_optimized
1630 1.2685 vmlinux eth_type_trans
1517 1.1805 vmlinux __qdisc_run
Thank you,
Drew
next prev parent reply other threads:[~2008-08-13 16:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 0:56 CPU utilization increased in 2.6.27rc Andrew Gallatin
2008-08-13 1:05 ` David Miller
2008-08-13 15:06 ` Andrew Gallatin
2008-08-13 1:15 ` David Miller
2008-08-13 16:13 ` Andrew Gallatin [this message]
2008-08-13 19:52 ` Robert Olsson
2008-08-13 21:34 ` Stephen Hemminger
2008-08-13 21:56 ` Robert Olsson
2008-08-13 22:06 ` Stephen Hemminger
2008-08-13 22:21 ` Robert Olsson
2008-08-13 20:03 ` Andi Kleen
2008-08-13 20:36 ` Andrew Gallatin
2008-08-13 20:27 ` David Miller
2008-08-13 20:58 ` Andrew Gallatin
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=48A30834.4090802@myri.com \
--to=gallatin@myri.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=robert@robur.slu.se \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.