From: Richard Scobie <richard@sauce.co.nz>
To: Chris Friesen <cfriesen@nortel.com>
Cc: e1000-list <e1000-devel@lists.sourceforge.net>,
Linux Network Development list <netdev@vger.kernel.org>,
"Allan, Bruce W" <bruce.w.allan@intel.com>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"Ronciak, John" <john.ronciak@intel.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"gospo@redhat.com" <gospo@redhat.com>
Subject: Re: behaviour question for igb on nehalem box
Date: Sat, 17 Oct 2009 11:15:37 +1300 [thread overview]
Message-ID: <4AD8F089.9010602@sauce.co.nz> (raw)
In-Reply-To: <4AD4B9BB.3010209@nortel.com>
I'm have just put together a Nehalem system (1 x Xeon),
2.6.30.8-64.fc11.x86_64, which has quad onboard 82576 and noticed during
testing using just a single interface, that the RX queues on the other 3
were receiving interrupts - observed in /proc/interrupts.
Is this normal behaviour?
Regards,
Richard
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
next prev parent reply other threads:[~2009-10-16 22:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 18:43 behaviour question for igb on nehalem box Chris Friesen
2009-10-09 20:22 ` Brandeburg, Jesse
2009-10-09 22:31 ` Chris Friesen
2009-10-09 23:20 ` Alexander Duyck
2009-10-09 23:48 ` Alexander Duyck
2009-10-13 17:32 ` Chris Friesen
2009-10-16 22:15 ` Richard Scobie [this message]
2009-10-16 22:48 ` [E1000-devel] " Brandeburg, Jesse
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=4AD8F089.9010602@sauce.co.nz \
--to=richard@sauce.co.nz \
--cc=bruce.w.allan@intel.com \
--cc=cfriesen@nortel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.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).