All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 09 May 2006 14:35:28 +0200	[thread overview]
Message-ID: <44608C90.30909@de.ibm.com> (raw)
In-Reply-To: <adafyjomsrd.fsf@cisco.com>

Roland Dreier wrote:
>     Heiko> Originaly, we had the same idea as you mentioned, that it
>     Heiko> would be better to do this in the higher levels. The point
>     Heiko> is that we can't see so far any simple posibility how this
>     Heiko> can done in the OpenIB stack, the TCP/IP network layer or
>     Heiko> somewhere in the Linux kernel.
> 
>     Heiko> For example: For IPoIB we get the best throughput when we
>     Heiko> do the CQ callbacks on different CPUs and not to stay on
>     Heiko> the same CPU.
> 
> So why not do it in IPoIB then?  This approach is not optimal
> globally.  For example, uverbs event dispatch is just going to queue
> an event and wake up the process waiting for events, and doing this on
> some random CPU not related to the where the process will run is
> clearly the worst possible way to dispatch the event.

Yes, I agree. It would not be an optimal solution, because other upper
level protocols (e.g. SDP, SRP, etc.) or userspace verbs would not be
affected by this changes. Nevertheless, how can an improved "scaling"
or "SMP" version of IPoIB look like. How could it be implemented?

>     Heiko> In other papers and slides (see [1]) you can see similar
>     Heiko> approaches.
> 
>     Heiko> [1]: Speeding up Networking, Van Jacobson and Bob
>     Heiko> Felderman,
>     Heiko> http://www.lemis.com/grog/Documentation/vj/lca06vj.pdf

> I think you've misunderstood this paper.  It's about maximizing CPU
> locality and pushing processing directly into the consumer.  In the
> context of slide 9, what you've done is sort of like adding another
> control loop inside the kernel, since you dispatch from interrupt
> handler to driver thread to final consumer.  So I would argue that
> your approach is exactly the opposite of what VJ is advocating.

Sorry, my idea was not to use the *.pdf file how it should be
implemented. I only wanted to show that other people are also thinking
about how TCP/IP performance could be increased and where the bottlenecks
(e.g. SOFTIRQs) are. :)

Regards,
	Heiko

  reply	other threads:[~2006-05-09 12:26 UTC|newest]

Thread overview: 31+ 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-04 21:29   ` Roland Dreier
2006-05-05 13:05   ` Heiko J Schick
2006-05-05 13:05     ` Heiko J Schick
2006-05-05 14:49     ` Roland Dreier
2006-05-09 12:35       ` Heiko J Schick [this message]
2006-05-09 16:23         ` Roland Dreier
2006-05-09 16:49           ` Michael S. Tsirkin
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:36                 ` Roland Dreier
2006-05-09 18:44                 ` Shirley Ma
2006-05-09 18:44               ` Michael S. Tsirkin
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:55                     ` Michael S. Tsirkin
2006-05-09 18:57             ` [openib-general] " Heiko J Schick
2006-05-09 19:04               ` Stephen Hemminger
2006-05-09 19:46               ` Shirley Ma
2006-05-09 20:20                 ` Michael S. Tsirkin
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-10  5:33                       ` Michael S. Tsirkin
2006-05-09 23:35           ` [openib-general] " Segher Boessenkool
2006-05-09 23:35             ` Segher Boessenkool
2006-05-09 13:15 ` Christoph Hellwig
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=44608C90.30909@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 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.