From: Jeff Garzik <jgarzik@pobox.com>
To: Nivedita Singhvi <niv@us.ibm.com>
Cc: Arjan van de Ven <arjanv@redhat.com>,
"Martin J. Bligh" <mbligh@aracnet.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
Andrew Morton <akpm@osdl.org>, Anton Blanchard <anton@samba.org>,
linux-kernel@vger.kernel.org, Netdev <netdev@oss.sgi.com>
Subject: Re: CONFIG_IRQBALANCE for AMD64?
Date: Fri, 28 May 2004 17:45:24 -0400 [thread overview]
Message-ID: <40B7B2F4.7080704@pobox.com> (raw)
In-Reply-To: <40B79DB0.6090209@us.ibm.com>
Long term, when NIC hardware is more advanced, we'll want something that
divides sockets/connections/etc. into per-CPU clusters... something
that's friendly to both SMP and NUMA+SMP configurations.
Or if enterprising companies get a clue, and open their NIC firmware, I
bet we could do this now.
Jeff
parent reply other threads:[~2004-05-28 21:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <40B79DB0.6090209@us.ibm.com>]
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=40B7B2F4.7080704@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=arjanv@redhat.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=netdev@oss.sgi.com \
--cc=niv@us.ibm.com \
/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).