From: Rick Jones <rick.jones2@hp.com>
To: Jesper Krogh <jesper@krogh.cc>
Cc: David Miller <davem@davemloft.net>,
yhlu.kernel@gmail.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: NIU - Sun Neptune 10g - Transmit timed out reset (2.6.24)
Date: Fri, 09 May 2008 16:33:37 -0700 [thread overview]
Message-ID: <4824DF51.9090902@hp.com> (raw)
In-Reply-To: <4824DAB0.8060604@krogh.cc>
Jesper Krogh wrote:
> Rick Jones wrote:
>
>>>> To which cpu(s) were the neptune's interrupts assigned? (grep <ethN>
>>>> /proc/interrupts)
>>>
>>>
>>> Several
>>
>>
>> Which ones?-) I suspect that since it is several that at least
>> answers the MSI_X question right? Or is it possible to have a single
>> device have several MSI interrupts?
Well, the output below anwered my question about multiple MSI's from a
single device :)
>
>
> The table is rather large.
> http://rafb.net/p/a9zfFA59.html
So, over time at least, the interrupts have been spread over half the
cores in the system. This is where the block diagram showing the socket
and I/O slot connections would be useful.
For the interrupts over a given interval, one can take snapshots at
either end of the interval and then run them through beforeafter:
ftp://ftp.cup.hp.com/dist/networking/tools/
I think that collectl might have something there too.
I guess the addresses in use weren't sufficient to get interrupts spread
across all 24 IRQ's.
rick jones
next prev parent reply other threads:[~2008-05-09 23:33 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 18:23 NIU - Sun Neptune 10g - Transmit timed out reset (2.6.24) Jesper Krogh
2008-05-07 18:30 ` Yinghai Lu
2008-05-07 21:15 ` David Miller
2008-05-09 18:32 ` Jesper Krogh
2008-05-09 21:32 ` David Miller
2008-05-09 21:59 ` Jesper Krogh
2008-05-09 22:07 ` David Miller
2008-05-09 22:13 ` Jesper Krogh
2008-05-09 22:09 ` Matheos Worku
2008-05-09 22:15 ` Jesper Krogh
2008-05-09 22:36 ` Matheos Worku
2008-05-09 22:43 ` Matheos Worku
2008-05-09 22:46 ` David Miller
2008-05-09 23:10 ` Jesper Krogh
2008-05-09 23:21 ` Matheos Worku
2008-05-09 22:45 ` David Miller
2008-05-22 16:32 ` Jesper Krogh
2008-05-22 17:15 ` Ben Hutchings
2008-05-22 17:41 ` David Miller
2008-05-22 18:14 ` Ben Hutchings
2008-05-22 18:28 ` David Miller
2008-06-01 7:25 ` Andrey Panin
2008-06-01 16:01 ` David Miller
2008-05-09 22:20 ` Rick Jones
2008-05-09 22:48 ` Jesper Krogh
2008-05-09 23:03 ` Rick Jones
2008-05-09 23:13 ` Jesper Krogh
2008-05-09 23:33 ` Rick Jones [this message]
2008-05-09 23:08 ` David Dillow
2008-05-10 6:22 ` Jesper Krogh
2008-05-10 15:53 ` Roland Dreier
2008-05-12 6:49 ` Jesper Krogh
2008-05-10 2:20 ` Bill Fink
2008-05-10 11:01 ` Jesper Krogh
2008-05-11 4:34 ` David Miller
2008-05-11 5:44 ` Jesper Krogh
2008-05-11 6:08 ` David Miller
2008-05-11 9:47 ` Jesper Krogh
2008-05-12 6:52 ` Jesper Krogh
2008-05-26 19:03 ` Jesper Krogh
2008-05-26 19:33 ` David Miller
2008-05-26 19:39 ` David Miller
2008-05-26 20:54 ` Jesper Krogh
2008-05-26 22:15 ` David Miller
2008-05-26 22:21 ` Jesper Krogh
2008-05-26 22:30 ` David Miller
2008-05-27 6:19 ` Jesper Krogh
2008-05-28 1:18 ` Matheos Worku
2008-05-29 5:34 ` David Miller
2008-05-30 0:14 ` Matheos Worku
2008-05-30 7:00 ` David Miller
2008-06-16 18:09 ` Matheos Worku
2008-06-16 18:21 ` Jesper Krogh
2008-06-18 0:02 ` David Miller
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=4824DF51.9090902@hp.com \
--to=rick.jones2@hp.com \
--cc=davem@davemloft.net \
--cc=jesper@krogh.cc \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yhlu.kernel@gmail.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.