From: Rick Jones <rick.jones2@hp.com>
To: sparclinux@vger.kernel.org
Subject: NIC interrupt assignments under UltraSPARC-T1
Date: Thu, 14 Sep 2006 20:17:15 +0000 [thread overview]
Message-ID: <4509B8CB.2070103@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 /proc/irq/mumble" I've used with
Linux on other (non-SPARC) hardware 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?
It has been suggested that I should be poking around in
arch/sparc64/kernel/irq.c and i've looked there, I'm still a bit lost as
I've not learned the heirarchy of the code in that area. With my
netperf stuff I've had the good fortune to not have to go any deeper
than getting a call to sched_setaffinity() right... I have noticed that
down in that file everything seems to be assuming a specific "CPU"
rather than a set of them (mask)
thanks,
rick jones
http://www.netperf.org/
next reply other threads:[~2006-09-14 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 20:17 Rick Jones [this message]
2006-09-19 20:04 ` NIC interrupt assignments under UltraSPARC-T1 David Miller
-- strict thread matches above, loose matches on Subject: below --
2006-09-14 0:47 Rick Jones
2006-09-14 1:14 ` 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=4509B8CB.2070103@hp.com \
--to=rick.jones2@hp.com \
--cc=sparclinux@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 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.