From: Andi Kleen <ak@suse.de>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: kernel performance update - 2.6.14-rc3
Date: 06 Oct 2005 12:32:11 +0200 [thread overview]
Message-ID: <p73mzlnylzo.fsf@verdi.suse.de> (raw)
In-Reply-To: <200510052115.j95LFgg07836@unix-os.sc.intel.com>
"Chen, Kenneth W" <kenneth.w.chen@intel.com> writes:
> Even though
> softirq is invoked at the end of dev_queue_xmit() via local_bh_enable(),
> not all execution of softirq will result a __wake_up(). With higher
> HZ rate, timer interrupt is more frequent and thus more softirq
> invocation and leads to more __wake_up(), which then takes us to higher
> throughput because cpu spend less time in idle.
This sounds like a serious bug somewhere if true.
-Andi
next prev parent reply other threads:[~2005-10-06 10:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 21:15 kernel performance update - 2.6.14-rc3 Chen, Kenneth W
2005-10-06 6:16 ` Arjan van de Ven
2005-10-06 10:04 ` Nick Piggin
2005-10-06 18:36 ` Chen, Kenneth W
2005-10-06 19:24 ` Sonny Rao
2005-10-06 19:32 ` Chen, Kenneth W
2005-10-06 10:32 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-08 0:49 Jon Burgess
2005-10-08 1:38 ` Chen, Kenneth W
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=p73mzlnylzo.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 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.