From: "Mark Ryden" <markryde@gmail.com>
To: netdev@vger.kernel.org
Subject: Two Dual Core processors and NICS (not handling interrupts on one CPU/assigning a Two Dual Core processors and NICS (not handling interrupts on one CPU / assigning a CPU to a NIC)
Date: Mon, 15 Jan 2007 11:15:52 +0200 [thread overview]
Message-ID: <dac45060701150115y5308f7b5ka44f2ea4ae304d4b@mail.gmail.com> (raw)
Hello,
I have a machine with 2 dual core CPUs. This machine runs Fedora Core 6.
I have two Intel e1000 GigaBit network cards on this machine; I use bonding so
that the machine assigns the same IP address to both NICs ;
It seems to me that bonding is configured OK, bacuse when running:
"cat /proc/net/bonding/bond0"
I get:
Ethernet Channel Bonding Driver: v3.0.3 (March 23, 2006)
Bonding Mode: load balancing (round-robin)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth0
MII Status: up
Link Failure Count: 1
Permanent HW addr: .....
Slave Interface: eth1
MII Status: up
Link Failure Count: 1
Permanent HW addr: ....
(And the Permanent HW addr is diffenet in these two entries).
I send a large amount of packets to this machine (more than 20,000 in
a second).
cat /proc/interrupts shops something like this:
CPU0 CPU1 CPU2 CPU3
50: 3359337 0 0 0 PCI-MSI eth0
58: 49 3396136 0 0 PCI-MSI eth1
CPU0 and CPU1 are of the first CPU as far as I understand ; so
this means as far as I understand that the second CPU (which has CPU3
and CPU4) does not handle
interrupts of the arrived packets; Can I somehow change it so the second
CPU will also handle network interrupts of receiving packets on the nic ?
Can I assign one CPU to eth0 and the second CPU to eth1 ?
Regards,
Mark
next reply other threads:[~2007-01-15 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 9:15 Mark Ryden [this message]
2007-01-15 9:58 ` Two Dual Core processors and NICS (not handling interrupts on one CPU/assigning a Two Dual Core processors and NICS (not handling interrupts on one CPU / assigning a CPU to a NIC) Robert Iakobashvili
2007-01-15 16:52 ` Auke Kok
2007-01-16 17:34 ` Rick Jones
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=dac45060701150115y5308f7b5ka44f2ea4ae304d4b@mail.gmail.com \
--to=markryde@gmail.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).