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

On Wed, 2006-27-12 at 14:08 +0100, Arjan van de Ven wrote:

> sure; however the kernel doesn't provide more accurate information
> currently (and I doubt it could even, it's not so easy to figure out
> which interface triggered the softirq if 2 interfaces share the cpu, and
> then, how much work came from which etc).
> 

If you sample CPU use and in between two samples you are able to know
which nic is tied to which CPU, how much cycles such cpu consumed in
user vs kernel, and how many packets were seen on such nic; then you
should have the info necessary to make a decision, no? Yes, I know it is
a handwave on my part and it is complex but by the same token, I would
suspect each kind of IO derived work (which results in interupts) will
have more inputs that could help you make a proper decision than a mere
glance of the interupts. I understand for example the SCSI subsystem
these days behaves very much like NAPI.
I think one of the failures of the APIC load balancing is a direct
result of not being able to factor in such enviromental factors.

> also the "amount of work" estimate doesn't need to be accurate to 5
> digits to be honest... just number of packets seems to be a quite
> reasonable approximation already. (if the kernel starts exporting more
> accurate data, irqbalance can easily use it of course)

It is certainly much more promising now than before. Most people will
probably have symettrical type of apps, so it should work for them.
For someone like myself i will still not use it because i typically dont
have symettrical loads.

cheers,
jamal
 


  reply	other threads:[~2006-12-27 14:44 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
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 [this message]
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=1167230668.3807.37.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.