From: Heiko J Schick <schihei@de.ibm.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: linux-kernel@vger.kernel.org, openib-general@openib.org,
	linuxppc-dev@ozlabs.org, Christoph Raisch <RAISCH@de.ibm.com>,
	Hoang-Nam Nguyen <HNGUYEN@de.ibm.com>,
	Marcus Eder <MEDER@de.ibm.com>
Subject: Re: [openib-general] [PATCH 07/16] ehca: interrupt handling routines
Date: Fri, 05 May 2006 15:05:45 +0200	[thread overview]
Message-ID: <445B4DA9.9040601@de.ibm.com> (raw)
In-Reply-To: <adaejz9o4vh.fsf@cisco.com>
Hello Roland,
Roland Dreier wrote:
> It seems that you are deferring completion event dispatch into threads
> spread across all the CPUs.  This seems like a very strange thing to
> me -- you are adding latency and possibly causing cacheline pingpong.
> 
> It may help throughput in some cases to spread the work across
> multiple CPUs but it seems strange to me to do this in the low-level
> driver.  My intuition would be that it would be better to do this in
> the higher levels, and leave open the possibility for protocols that
> want the lowest possible latency to be called directly from the
> interrupt handler.
We've implemented this "spread CQ callbacks across multiple CPUs"
functionality to get better throughput on a SMP system, as you have
seen.
Originaly, we had the same idea as you mentioned, that it would be better
to do this in the higher levels. The point is that we can't see so far
any simple posibility how this can done in the OpenIB stack, the TCP/IP
network layer or somewhere in the Linux kernel.
For example:
For IPoIB we get the best throughput when we do the CQ callbacks on
different CPUs and not to stay on the same CPU.
In other papers and slides (see [1]) you can see similar approaches.
I think such one implementation or functionality could require more
or less a non-trivial changes. This could be also releated to other
I/O traffic.
[1]:  Speeding up Networking, Van Jacobson and Bob Felderman,
       http://www.lemis.com/grog/Documentation/vj/lca06vj.pdf
Regards,
	Heiko
next prev parent reply	other threads:[~2006-05-05 13:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-27 10:48 [PATCH 07/16] ehca: interrupt handling routines Heiko J Schick
2006-05-04 21:29 ` [openib-general] " Roland Dreier
2006-05-05 13:05   ` Heiko J Schick [this message]
2006-05-05 14:49     ` Roland Dreier
2006-05-09 12:35       ` Heiko J Schick
2006-05-09 16:23         ` Roland Dreier
2006-05-09 16:49           ` Michael S. Tsirkin
2006-05-09 18:27             ` [openib-general] " Shirley Ma
2006-05-09 18:36               ` Roland Dreier
2006-05-09 18:44                 ` Shirley Ma
2006-05-09 18:44               ` Michael S. Tsirkin
2006-05-09 18:51                 ` Shirley Ma
2006-05-09 18:55                   ` Michael S. Tsirkin
2006-05-09 18:57             ` [openib-general] " Heiko J Schick
2006-05-09 19:46               ` Shirley Ma
2006-05-09 20:20                 ` Michael S. Tsirkin
2006-05-09 21:28                   ` Shirley Ma
2006-05-10  5:33                     ` Michael S. Tsirkin
2006-05-09 23:35           ` [openib-general] " Segher Boessenkool
2006-05-09 13:15 ` Christoph Hellwig
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=445B4DA9.9040601@de.ibm.com \
    --to=schihei@de.ibm.com \
    --cc=HNGUYEN@de.ibm.com \
    --cc=MEDER@de.ibm.com \
    --cc=RAISCH@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=openib-general@openib.org \
    --cc=rdreier@cisco.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).