From: "Xiaoliang \(David\) Wei" <weixl@caltech.edu>
To: "Ben Greear" <greearb@candelatech.com>
Cc: <netdev@oss.sgi.com>
Subject: Re: How can we bound one CPU to one Gigabit NIC?
Date: Mon, 7 Oct 2002 12:12:51 -0700 [thread overview]
Message-ID: <003401c26e35$890d56b0$f5f2010a@weixl> (raw)
In-Reply-To: 3DA1D15C.1070309@candelatech.com
Thanks Ben. We are going to use SysKonnect Cards. Are they tg3 based, too?
Thank you.
Xiaoliang (David) Wei Graduate Student in CS@Caltech
http://www.cs.caltech.edu/~weixl
====================================================
----- Original Message -----
From: "Ben Greear" <greearb@candelatech.com>
To: "Xiaoliang (David) Wei" <weixl@caltech.edu>
Cc: <netdev@oss.sgi.com>
Sent: Monday, October 07, 2002 11:24 AM
Subject: Re: How can we bound one CPU to one Gigabit NIC?
> Xiaoliang (David) Wei wrote:
> > 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.:)
>
> My experiments show you will still get re-ordered packets occasionally
> (but then again, I'm having other wierd problems, so maybe you wont).
>
> # Bind processor 2 (1<<1) to irq 11
> echo 2 > /proc/irq/11/smp_affinity
>
> # Bind processor 1 (1<<0) to irq 19
> echo 1 > /proc/irq/9/smp_affinity
>
>
> I will be interested to hear of your results, as I have been having
> heating problems with e1000 and other problems with tg3 based nics!
>
> Ben
>
> >
> >
> >
> > Xiaoliang (David) Wei Graduate Student in CS@Caltech
> > http://www.cs.caltech.edu/~weixl
> > ====================================================
> >
>
>
> --
> Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
> President of Candela Technologies Inc http://www.candelatech.com
> ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
>
>
>
>
next prev parent reply other threads:[~2002-10-07 19:12 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 ` How can we bound one CPU to one Gigabit NIC? Xiaoliang (David) Wei
2002-10-07 18:24 ` Ben Greear
2002-10-07 19:12 ` Xiaoliang (David) Wei [this message]
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='003401c26e35$890d56b0$f5f2010a@weixl' \
--to=weixl@caltech.edu \
--cc=greearb@candelatech.com \
--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 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).