All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: "Ma, Chinang" <chinang.ma@intel.com>
Cc: Rick Jones <rick.jones2@hp.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Jeff Garzik <jeff@garzik.org>,
	"andi@firstfloor.org" <andi@firstfloor.org>,
	"arjan@infradead.org" <arjan@infradead.org>,
	"jens.axboe@oracle.com" <jens.axboe@oracle.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Styner, Douglas W" <douglas.w.styner@intel.com>,
	"Prickett, Terry O" <terry.o.prickett@intel.com>,
	"Wilcox, Matthew R" <matthew.r.wilcox@intel.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Subject: Re: >10% performance degradation since 2.6.18
Date: Mon, 6 Jul 2009 12:53:53 -0600	[thread overview]
Message-ID: <20090706185353.GY5480@parisc-linux.org> (raw)
In-Reply-To: <BC02C49EEB98354DBA7F5DD76F2A9E800357E11D67@azsmsx501.amr.corp.intel.com>

On Mon, Jul 06, 2009 at 11:48:47AM -0700, Ma, Chinang wrote:
> On the distributing interrupt load subject.  Can we do the same thing with the IOC interrupts. We have 4 LSI 3801, The number of i/o interrupt is huge on 4 of the cpus. Is there a way to divide the IOC irq number so we can spread out the i/o interrupt to more cpu?

I think the LSI 3801 only has one interrupt per ioc, but they could
perhaps be better spread-out.  Right now, they're delivering interrupts
to CPUs 2, 3, 4 and 5.  Possibly spreading them out to CPUs 2, 6, 10
and 14 would help.  Or maybe it would hurt ...

(nb: the ioc interrupts are similarly tied to CPUs 2, 3, 4 and 5 with
2.6.18, so this isn't a likely cause of/solution to the regression,
it may just be a path to better numbers).

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  reply	other threads:[~2009-07-06 18:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-03  2:56 >10% performance degradation since 2.6.18 Matthew Wilcox
2009-07-03 17:04 ` Paul E. McKenney
2009-07-03 18:19 ` Andi Kleen
2009-07-03 18:54   ` Jens Axboe
2009-07-03 19:13     ` Matthew Wilcox
2009-07-03 19:22       ` Jens Axboe
2009-07-03 19:45         ` Matthew Wilcox
2009-07-03 19:54           ` Andi Kleen
2009-07-03 20:04             ` Arjan van de Ven
2009-07-03 23:35               ` Andi Kleen
2009-07-04  6:04                 ` Arjan van de Ven
2009-07-04  8:44                   ` Andi Kleen
2009-07-04  9:19                     ` Jeff Garzik
2009-07-05  4:01                       ` Herbert Xu
2009-07-05 13:09                         ` Matthew Wilcox
2009-07-05 16:11                           ` Herbert Xu
2009-07-06  8:38                           ` Andi Kleen
2009-07-05 20:44                         ` Jeff Garzik
2009-07-06  1:19                           ` Herbert Xu
2009-07-06  8:45                           ` Andi Kleen
2009-07-06 17:00                         ` Rick Jones
2009-07-06 17:36                           ` Ma, Chinang
2009-07-06 17:42                             ` Matthew Wilcox
2009-07-06 17:57                               ` Ma, Chinang
2009-07-06 18:05                                 ` Matthew Wilcox
2009-07-06 18:48                                   ` Ma, Chinang
2009-07-06 18:53                                     ` Matthew Wilcox [this message]
2009-07-06 21:16   ` Ma, Chinang
2009-07-07  8:16     ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2009-07-05 11:00 Daniel J Blueman
2009-07-06 21:58 ` Chetan.Loke
2009-07-07 22:05   ` Daniel J Blueman
2009-07-08 15:03     ` Chetan.Loke

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=20090706185353.GY5480@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=andi@firstfloor.org \
    --cc=arjan@infradead.org \
    --cc=chinang.ma@intel.com \
    --cc=douglas.w.styner@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=jeff@garzik.org \
    --cc=jens.axboe@oracle.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.r.wilcox@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=rick.jones2@hp.com \
    --cc=terry.o.prickett@intel.com \
    /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.