From: Rick Jones <rick.jones2@hp.com>
To: 7eggert@gmx.de
Cc: Kok@vger.kernel.org, Auke <auke-jan.h.kok@intel.com>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Anton Titov <a.titov@host.bg>, Chris Snook <csnook@redhat.com>,
"H. Willstrand" <h.willstrand@gmail.com>,
netdev@vger.kernel.org,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Re: Bad network performance over 2Gbps
Date: Mon, 21 Apr 2008 09:42:00 -0700 [thread overview]
Message-ID: <480CC3D8.3040700@hp.com> (raw)
In-Reply-To: <E1JnEcl-0000xc-D9@be1.7eggert.dyndns.org>
Bodo Eggert wrote:
> Kok, Auke <auke-jan.h.kok@intel.com> wrote:
>
>
>>[X86] IRQBALANCE: Mark as BROKEN and disable by default
>>
>>The IRQBALANCE option causes interrupts to bounce all around on SMP systems
>>quickly burying the CPU in migration cost and cache misses. Mainly affected
>>are network interrupts and this results in one CPU pegged in softirqd
>>completely.
>
>
> If this is the problem, maybe it would help to only balance the IRQs each
> e.g. ten seconds? Unfortunately I have no SMP system to try it out.
Be it kernel or user space, for consistent benchmark results it needs to
be able to be turned-off without turning the code. That leaves me in
agreement with Stephen that if it must exist, the user space one would
be preferable. It can be easily terminated with extreme prejudice.
rick jones
next prev parent reply other threads:[~2008-04-21 16:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aiXVe-Yn-7@gated-at.bofh.it>
[not found] ` <ajGfA-7rt-9@gated-at.bofh.it>
[not found] ` <ajGfA-7rt-11@gated-at.bofh.it>
[not found] ` <ajGfA-7rt-13@gated-at.bofh.it>
[not found] ` <ajGfA-7rt-15@gated-at.bofh.it>
[not found] ` <ajGfA-7rt-7@gated-at.bofh.it>
2008-04-19 15:05 ` [PATCH] Re: Bad network performance over 2Gbps Bodo Eggert
[not found] ` <E1JnEcl-0000xc-D9@be1.7eggert.dyndns.org>
2008-04-19 19:23 ` Stephen Hemminger
2008-04-21 16:42 ` Rick Jones [this message]
2008-04-21 19:52 ` Bodo Eggert
2008-04-21 20:02 ` Rick Jones
2008-04-21 21:08 ` Bodo Eggert
2008-04-21 21:30 ` Chris Snook
2008-04-22 7:36 ` Bodo Eggert
2008-04-22 17:46 ` Kok, Auke
[not found] <1208282804.23631.27.camel@localhost>
2008-04-15 20:15 ` H. Willstrand
2008-04-15 20:34 ` Kok, Auke
2008-04-15 20:59 ` Chris Snook
2008-04-17 10:02 ` Anton Titov
2008-04-17 17:37 ` [PATCH] " Kok, Auke
2008-04-20 12:08 ` Denys Fedoryshchenko
2008-04-21 13:19 ` Pavel Machek
2008-04-21 16:38 ` Kok, Auke
2008-04-21 15:28 ` Ingo Molnar
2008-04-21 16:58 ` Kok, Auke
2008-04-21 18:35 ` Andi Kleen
2008-04-22 5:07 ` Bill Fink
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=480CC3D8.3040700@hp.com \
--to=rick.jones2@hp.com \
--cc=7eggert@gmx.de \
--cc=Kok@vger.kernel.org \
--cc=a.titov@host.bg \
--cc=akpm@linux-foundation.org \
--cc=auke-jan.h.kok@intel.com \
--cc=csnook@redhat.com \
--cc=h.willstrand@gmail.com \
--cc=hpa@zytor.com \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).