netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Nivedita Singhvi <niv@us.ibm.com>
Cc: Cheng Jin <chengjin@cs.caltech.edu>,
	satya srikanth <satyasrikanth2001@yahoo.com>,
	"Xiaoliang (David) Wei" <weixl@caltech.edu>,
	"netdev@oss.sgi.com" <netdev@oss.sgi.com>
Subject: Re: gigabit ethernet
Date: Fri, 13 Feb 2004 17:11:09 -0500	[thread overview]
Message-ID: <20040213221108.GA16586@gtf.org> (raw)
In-Reply-To: <402D424A.5060901@us.ibm.com>

On Fri, Feb 13, 2004 at 01:31:54PM -0800, Nivedita Singhvi wrote:
> Cheng Jin wrote:
> >
> >I read somewhere that Intel SMP has cpu0 taking care of 
> >all the hardware interrupts, but I don't know about softirqs.
> >I think all softirqs related to the GbE are handled by the
> >same cpu.
> 
> For incoming network packets, the hw interrupt handler simply
> schedules a local softirq to handle the rest of the input
> processing. So the softirq will execute on the same
> CPU that the hw interrupt came in on.

Many answers ;-)

1) Starting with Pentium4, all interrupts are delivered to cpu0...
unless software directs otherwise.  Thus it is helpful to have a
software irq balancing solution.  Red Hat has a userspace irqbalanced,
and kernel 2.6.x also has kirqd on x86.

2) For networking, receiving all packets on one cpu has many benefits,
and avoids packet reordering problems that occasionally appear on SMP.

3) For NAPI drivers, regardless of interrupt balancing strategy, packets
are usually receiving on one cpu.

  reply	other threads:[~2004-02-13 22:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-12  8:39 gigabit ethernet satya srikanth
2004-02-12  9:34 ` Xiaoliang (David) Wei
2004-02-13 10:38   ` satya srikanth
2004-02-13 19:36     ` Cheng Jin
2004-02-13 21:31       ` Nivedita Singhvi
2004-02-13 22:11         ` Jeff Garzik [this message]
2004-02-14 14:09       ` satya srikanth
2004-02-16  4:32         ` Ben Greear

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=20040213221108.GA16586@gtf.org \
    --to=jgarzik@pobox.com \
    --cc=chengjin@cs.caltech.edu \
    --cc=netdev@oss.sgi.com \
    --cc=niv@us.ibm.com \
    --cc=satyasrikanth2001@yahoo.com \
    --cc=weixl@caltech.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).