linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean Hefty <mshefty@ichips.intel.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: linux-kernel@vger.kernel.org, general@lists.openfabrics.org
Subject: Re: [ofa-general] Further 2.6.23 merge plans...
Date: Thu, 12 Jul 2007 18:14:27 -0700	[thread overview]
Message-ID: <4696D1F3.2040507@ichips.intel.com> (raw)
In-Reply-To: <adahco943ip.fsf@cisco.com>

>  - Take a look at Sean's local SA caching patches.  I merged
>    everything else from Sean's tree, but I'm still undecided about
>    these.  I haven't read them carefully yet, but even aside from that
>    I don't have a good feeling about whether there's consensus about
>    this yet.  Any opinions about merging, for or against, would be
>    appreciated here.

Obviously I'm biased here, but we've definitely seen local caching of 
path records (PR) greatly improve performance for large MPI job runs. 
(Our largest jobs wouldn't run without it.)  The development of the 
feature was requested and paid for by the US national labs. 
Infinicon/Silverstorm/QLogic also had this feature in their IB stack for 
scalability reasons as well.  PR caching is done in the stack today by 
IPoIB.

The implementation is hidden under the current kernel ib_sa interface, 
is disabled by default, and automatically fails over to standard PR 
queries if needed.  Removing the cache later should be fairly easy.

But to be fair, it will be difficult to enable both QoS and local PR 
caching.  To me, this would be the strongest reason against using it. 
However, QoS places additional burden on the SA, which will make scaling 
even more challenging.

- Sean

  parent reply	other threads:[~2007-07-13  1:14 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12 23:07 [GIT PULL] please pull infiniband.git Roland Dreier
2007-07-12 23:15 ` Further 2.6.23 merge plans Roland Dreier
2007-07-13  0:17   ` [ofa-general] " Hal Rosenstock
2007-07-13  1:14   ` Sean Hefty [this message]
     [not found]     ` <15ddcffd0707172020j5b68fcb2v7d3ca77863998020@mail.gmail.com>
2007-07-18  3:23       ` Roland Dreier
2007-07-18  5:26         ` Sean Hefty
2007-07-18 17:05           ` Sean Hefty
2007-07-18 20:54             ` Sean Hefty
2007-07-13  5:47   ` Michael S. Tsirkin
2007-07-13 18:14     ` Roland Dreier
2007-07-13 18:50       ` [ofa-general] " Shirley Ma
2007-07-17 18:06         ` Roland Dreier
2007-07-14 17:54       ` Michael S. Tsirkin
     [not found]         ` <OF72F6B9D1.F60C4EEF-ON8725731A.00506757-8825731A.0024BD1C@us.ibm.com>
2007-07-16 14:55           ` [ofa-general] " Michael S. Tsirkin
2007-07-16 16:42         ` Roland Dreier
2007-07-16 20:05           ` Michael S. Tsirkin
2007-07-17 17:53             ` Roland Dreier
2007-07-13 18:56   ` [ofa-general] " Shirley Ma
2007-07-16 16:47     ` Roland Dreier
2007-07-15 12:26   ` Tziporet Koren
2007-07-16 16:42     ` Roland Dreier
2007-07-17 18:07   ` Roland Dreier
2007-07-17 20:43     ` Matt Leininger
2007-07-17 20:45       ` Roland Dreier
2007-07-18  6:36         ` Or Gerlitz
2007-07-17 21:44     ` Michael S. Tsirkin
2007-07-18  7:34       ` [ofa-general] " Tziporet Koren
2007-07-18  7:38         ` Michael S. Tsirkin
2007-07-18  8:48           ` Tziporet Koren
2007-07-18 16:16             ` Sean Hefty
2007-07-18 16:20               ` Roland Dreier

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=4696D1F3.2040507@ichips.intel.com \
    --to=mshefty@ichips.intel.com \
    --cc=general@lists.openfabrics.org \
    --cc=linux-kernel@vger.kernel.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).