All of lore.kernel.org
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: Robert Iakobashvili <coroberti@gmail.com>
Cc: Arjan van de Ven <arjan@infradead.org>, netdev@vger.kernel.org
Subject: Re: Network card IRQ balancing with Intel 5000 series chipsets
Date: Wed, 27 Dec 2006 09:31:19 -0500	[thread overview]
Message-ID: <1167229879.3807.24.camel@localhost> (raw)
In-Reply-To: <7e63f56c0612262309p5337a753q3b1748910fce70b5@mail.gmail.com>

On Wed, 2006-27-12 at 09:09 +0200, Robert Iakobashvili wrote:

> 
> My scenario is treatment of RTP packets in kernel space with a single network
> card (both Rx and Tx). The default of the Intel 5000 series chipset is
> affinity of each
> network card to a certain CPU. Currently, neither with irqbalance nor
> with kernel
> irq-balancing (MSI and io-apic attempted) I do not find a way to
> balance that irq.

In the near future, when the NIC vendors wake up[1] because CPU vendors
- including big bad Intel -  are going to be putting out a large number
of hardware threads, you should be able to do more clever things with
such a setup. At the moment, just tie it to a single CPU and have your
other processes that are related running/bound on the other cores so you
can utilize them. OTOH, you say you are only using 30% of the one CPU,
so it may not be a big deal to tie your single nic to on cpu.

cheers,
jamal

[1] If you are able to change the NIC in your setup try looking at
netiron;  email Leonid.Grossman@netiron.com they have a much clever nic
than the e1000. It has multiple DMA receive rings which are selectable
via a little classifier (example you could have RTP going to CPU0 and
rest going to CPU1). The DMA rings could be tied to different
interupts/MSI and with some little work could be made to appear like
several interfaces.


  reply	other threads:[~2006-12-27 14:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-24  9:34 Network card IRQ balancing with Intel 5000 series chipsets Robert Iakobashvili
2006-12-25  9:35 ` Arjan van de Ven
2006-12-25 11:26   ` Robert Iakobashvili
2006-12-25 11:34     ` Arjan van de Ven
2006-12-25 12:54       ` Robert Iakobashvili
2006-12-26 18:44         ` jamal
2006-12-26 19:51           ` Robert Iakobashvili
2006-12-26 22:11             ` jamal
2007-01-02 17:56               ` Rick Jones
2006-12-26 22:06           ` Arjan van de Ven
2006-12-26 22:46             ` jamal
2006-12-27  0:28               ` Arjan van de Ven
2006-12-27  3:47                 ` jamal
2006-12-27  7:09                   ` Robert Iakobashvili
2006-12-27 14:31                     ` jamal [this message]
2006-12-29  2:04                       ` Krzysztof Oledzki
2006-12-29 17:36                         ` Robert Iakobashvili
2006-12-27 13:08                   ` Arjan van de Ven
2006-12-27 14:44                     ` jamal
2006-12-27 15:06                       ` Arjan van de Ven
2007-01-02 17:57                 ` Rick Jones

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=1167229879.3807.24.camel@localhost \
    --to=hadi@cyberus.ca \
    --cc=arjan@infradead.org \
    --cc=coroberti@gmail.com \
    --cc=netdev@vger.kernel.org \
    /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.