netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: Linux Network Development list <netdev@vger.kernel.org>
Subject: NIC interrupt assignments under UltraSPARC-T1
Date: Wed, 13 Sep 2006 17:47:27 -0700	[thread overview]
Message-ID: <4508A69F.8060102@hp.com> (raw)

 From time to time I "play" with netperf on different systems.  I happen 
to have occasion to play with a T2000.  Under Solaris 10 I am able to 
coerce the interrupts of the different core GbEs to be on different 
cores rather than strands of the same core.

Under a 2.6.15 kernel (Ubuntu Dapper) it would appear that the old 
standby of "echo affinity mask to the IRQ" doesn't "work" - no matter 
how I change the mask for a NIC, running a netperf TCP_RR test seems to 
show the interrupts happening on the same strand.

Is it indeed not possible to alter the interrupt assignments or have I 
(as I'm wont to do) missed something quasi-obvious?

thanks,

rick jones

             reply	other threads:[~2006-09-14  0:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14  0:47 Rick Jones [this message]
2006-09-14  1:14 ` NIC interrupt assignments under UltraSPARC-T1 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=4508A69F.8060102@hp.com \
    --to=rick.jones2@hp.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).