From: "Michael S. Tsirkin" <mst@mellanox.co.il>
To: linux-ia64@vger.kernel.org
Subject: Re: SDP perf drop with 2.6.15
Date: Thu, 12 Jan 2006 19:58:28 +0000 [thread overview]
Message-ID: <20060112195828.GD9256@mellanox.co.il> (raw)
In-Reply-To: <20060112195004.GK3106@esmail.cup.hp.com>
Quoting r. Grant Grundler <iod00d@hp.com>:
> Subject: Re: SDP perf drop with 2.6.15
>
> On Thu, Jan 12, 2006 at 09:18:03AM +0200, Michael S. Tsirkin wrote:
> > > Makes me think it's a change in the interrupt code path.
> > > Any clues on where I might start with this?
> >
> > oprofile should show where we are spending the time.
>
> Executive summary:
> Silly me. interrupt bindings changed and I didn't check after rolling
> to 2.6.15 (from 2.6.14). That explains the increase cpu utilization
> with lower performance.
> Getting similar performance with -T 0,0 (2.6.15) vs -T 1,1 (2.6.14).
>
OK, so we are left with the ref count now.
I'm seeing this myself sometimes, I have some other stuff to attend to
next week, and then I plan to look into this.
--
MST
next prev parent reply other threads:[~2006-01-12 19:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 19:50 SDP perf drop with 2.6.15 Grant Grundler
2006-01-12 19:58 ` Michael S. Tsirkin [this message]
2006-01-31 21:55 ` [openib-general] " Grant Grundler
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=20060112195828.GD9256@mellanox.co.il \
--to=mst@mellanox.co.il \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox