From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Snook Subject: Re: [PATCH] Re: Bad network performance over 2Gbps Date: Mon, 21 Apr 2008 17:30:36 -0400 Message-ID: <480D077C.3090509@redhat.com> References: <480CC3D8.3040700@hp.com> <480CF2C0.9050208@hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Rick Jones , Kok@vger.kernel.org, Auke , Ingo Molnar , Thomas Gleixner , "H. Peter Anvin" , Linux Kernel Mailing List , Anton Titov , "H. Willstrand" , netdev@vger.kernel.org, Jesse Brandeburg , Linus Torvalds , Andrew Morton To: Bodo Eggert <7eggert@gmx.de> Return-path: Received: from mx1.redhat.com ([66.187.233.31]:55359 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754909AbYDUVbe (ORCPT ); Mon, 21 Apr 2008 17:31:34 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: Bodo Eggert wrote: > On Mon, 21 Apr 2008, Rick Jones wrote: >> Bodo Eggert wrote: >>> On Mon, 21 Apr 2008, Rick Jones wrote: > >>>> 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. >>> >>> I agree that having a full-featured userspace balancer daemon with lots of >>> intelligence will be theoretically better, but if you can have a simple >>> daemon doing OK on many machines for less than the userspace daemon's >>> kernel stack, why not? >> Perhaps my judgement is too colored by benchmark(et)ing, and desires to have >> repeatable results on things like neperf, but I very much like to know where >> my interrupts are going and don't like them moving around. That is why I am >> not particularly fond of either flavor of irq balancing. >> >> That being the case, whatever is out there aught to be able to be disabled on >> a running system without having to roll bits or reboot. > > Adding a "module" parameter to disable it should be cheap, isn't it? Except the irq balancing is system-wide. Adding per-device exemptions to an obsolete feature seems like the wrong way to go. -- Chris