From: David Miller <davem@davemloft.net>
To: porterde@cs.utexas.edu
Cc: linux-net@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: e1000 softirq load balancing
Date: Tue, 14 Oct 2008 12:51:56 -0700 (PDT) [thread overview]
Message-ID: <20081014.125156.92616351.davem@davemloft.net> (raw)
In-Reply-To: <48F4ED7E.4070308@cs.utexas.edu>
From: Don Porter <porterde@cs.utexas.edu>
Date: Tue, 14 Oct 2008 14:05:34 -0500
> It seems to me that with 4 independent NICs and plenty of CPUs to
> spare, I ought to be able to assign one softirq daemon to each NIC
> rather than funnelling all of the traffic through 1 or 2.
Traffic doesn't get distributed unless the NIC has support
for RX flow seperation and PCI MSI-X interrupts. Your NICs
do not.
So no matter how hard you try, each NIC is going to have it's
packets processed essentially on one cpu.
next parent reply other threads:[~2008-10-14 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48F4ED7E.4070308@cs.utexas.edu>
2008-10-14 19:51 ` David Miller [this message]
2008-10-14 23:46 ` e1000 softirq load balancing Don Porter
2008-10-14 23:51 ` David Miller
2008-10-14 23:55 ` Donald Porter
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=20081014.125156.92616351.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-net@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=porterde@cs.utexas.edu \
/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).