netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:03:12 -0700	[thread overview]
Message-ID: <4824D830.9090504@hp.com> (raw)
In-Reply-To: <4824D4C0.10201@krogh.cc>

>> 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?

>> Is the irqbalanced running?
> 
> 
> Yes. I started by not running it, but saw that cpu 0 was saturated by
> ksoftirqd
> 
>> Were any of the 16 CPUs in the system saturated during the test? (top 
>> with all CPUs displayed)
> 
> 
> Yes..
> Cpu12 : 34.2%us,  5.9%sy,  0.0%ni,  0.0%id, 14.5%wa,  1.0%hi, 44.4%si, 
> 0.0%st

David mentioned TX serialization - perhaps that is where TX completions 
are happening?

> All others have idle time.
> 
>> Do you have/know of any diagrams showing the way the I/O slots are 
>> wired to the rest of the system?
> 
> 
> I havent dug into that. Probably naive, as I as, I expected som hardware
> guys as Sun to have taken care of that, when I bought the recommended
> 10g card for their own server.

I am very clueless as to the design considerations under which Neptune 
was designed, but given that Neptune is based (IIRC) on the same "in 
core" 10G stuff as Sun talks about being in the UltraSPARC-T2 
processors, there is the possibility the design center was somewhat 
different then what one sees in an 8P Opteron system, whether it carries 
a Sun logo or not.  From what I've learned thusfar 8P Opteron systems 
are "interesting" beasts with what I suspect are rather different 
constraints and behaviours than an UltraSPARC-T[12] system.

What I was asking about was more a block diagram showing via which 
sockets the given I/O slots were connected.

>> Have you tried any tests without any filesystem involvement? 
> 
> no not yet. I'll try that.

If you decide to go the netperf route, feel free to contact me directly 
with netperf questions, or via the netperf-talk mailling list on 
netperf.org.

rick jones


  reply	other threads:[~2008-05-09 23:03 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4821F3B7.2090702@krogh.cc>
     [not found] ` <86802c440805071130m62c1f4edydb3316dac4a2aba2@mail.gmail.com>
2008-05-07 21:15   ` NIU - Sun Neptune 10g - Transmit timed out reset (2.6.24) 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 [this message]
2008-05-09 23:13                 ` Jesper Krogh
2008-05-09 23:33                   ` Rick Jones
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=4824D830.9090504@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 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).