All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Xiaoliang \(David\) Wei" <weixl@caltech.edu>
To: <netdev@oss.sgi.com>
Subject: How can we bound one CPU to one Gigabit NIC?
Date: Mon, 7 Oct 2002 11:11:50 -0700	[thread overview]
Message-ID: <03ab01c26e2d$06adeac0$f5f2010a@weixl> (raw)
In-Reply-To: Pine.GSO.4.30.0210070749430.1861-100000@shell.cyberus.ca

Hi Everyone,
      I am now doing some experiments on Dual CPU (2.4Ghz) with 2 Gigabit
cards. Can anyone tell me how to bound one CPU to each NIC so that we don't
need to care about the packet-reordering and the interrupt sharing problems?
      Thank you very much.:)



Xiaoliang (David) Wei             Graduate Student in CS@Caltech
http://www.cs.caltech.edu/~weixl
====================================================

  parent reply	other threads:[~2002-10-07 18:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-06  3:38 Update on e1000 troubles (over-heating!) Ben Greear
2002-10-06  3:47 ` Andre Hedrick
2002-10-06 22:38   ` jamal
2002-10-07  0:14     ` Andre Hedrick
2002-10-07 11:56       ` jamal
2002-10-09  1:10         ` Update on e1000 troubles (over-heating!) (problem solved) Ben Greear
2002-10-07  3:46     ` Update on e1000 troubles (over-heating!) Ben Greear
2002-10-07  5:26       ` David S. Miller
2002-10-07 11:53       ` jamal
2002-10-07 11:58         ` David S. Miller
2002-10-07 16:40         ` Ben Greear
2002-10-07 18:11         ` Xiaoliang (David) Wei [this message]
2002-10-07 18:24           ` How can we bound one CPU to one Gigabit NIC? Ben Greear
2002-10-07 19:12             ` Xiaoliang (David) Wei
2002-10-08  7:27             ` Xiaoliang (David) Wei
2002-10-08  8:57               ` jamal
2002-10-08 17:41                 ` Jason Lunz
2002-10-10  2:22                   ` jamal
2002-10-10  2:24                     ` jamal

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='03ab01c26e2d$06adeac0$f5f2010a@weixl' \
    --to=weixl@caltech.edu \
    --cc=netdev@oss.sgi.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 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.